Selenium Wire not working with zyte-smartproxy-headless-proxy
See original GitHub issueDear selenium-wire,
I have been using proxy running in my localhost port 3128 and it is working in normal selenium.
I guess that the command: chrome_options.add_argument("--proxy-server=localhost:3128")
for selenium-wire is not working.
Any idea of solving this?
Thanks a lot
Issue Analytics
- State:
- Created 2 years ago
- Comments:63 (25 by maintainers)
Top Results From Across the Web
Using Smart Proxy Manager with Selenium Wire
Selenium Wire requires Selenium python libraries, WebDriver installed and an active Smart Proxy Manager account. Log in or signup here.
Read more >Selenium with proxy not working / wrong options?
There are a couple of things you need to look back: First of all, there seems be a typo. There is a space...
Read more >selenium wire headless的推薦與評價 - 韓流韓星資訊站
Selenium Wire not working with zyte-smartproxy-headless-proxy #322. Dear selenium-wire,. I have been using proxy running in my localhost port 3128 and it is ......
Read more >selenium-wire 1.0.12 - PyPI
The requests are just a list and can be iterated (like in the opening example) ... If you ask too soon, then you...
Read more >selenium-wire - Python Package Health Analysis - Snyk
Install using pip: pip install selenium-wire. If you get an error about not being able to build cryptography you may be running an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@AndreuJove , @wkeeling had the same issue, managed to fix it by
pip3 install -U cryptography
. Cryptography module was outdated.hey everyone! I’m Júlio e developer from Zyte and I’ve been investigating the issue over the last couple of days. It is not related to our servers, but related to a library we developed to link the containers with our servers to store the scraping results.
In this library we call
socket.setdefaulttimeout
which seems to cause some issues withpyOpenSSL
I’ve created an issue on our library to investigate if we can overcome it somehow https://github.com/scrapinghub/scrapinghub-entrypoint-scrapy/issues/62In that issue you’ll find a link to the issue in
pyOpenSSL
and it seems they provide some approaches to fix the issue when usingpyOpenSSL
. Maybe you can check if it makes sense to add this fix toselenium-wire
as well as it will fail in any case that the user calledsocket.setdefaulttimeout