search

Cuadrix / puppeteer-page-proxy

Additional module to use with 'puppeteer' for setting proxies per page basis.
428 stars 100 forks source link

Doesn't work for me #53

Closed Nisthar closed 2 years ago

Nisthar commented 3 years ago

I used your example code with proxies from http://free-proxy.cz/en/

ice_screenshot_20201125-124928

All other tabs work correctly.

pkmnmstr98 commented 3 years ago

Show us some code please lol

CedricBrandt commented 3 years ago

Also experiencing this for HTTPS traffic only. Any workaround for this?

CedricBrandt commented 3 years ago

For me this was occuring because I used an outdated version of HttpsProxyAgent in the same project. After npm update it was fixed for me

Maxou44 commented 3 years ago

I had the same error, when we use a HTTPS proxy, we should use the domain name as host, we can't use an IP address or the security handshake with the proxy will fail.

https://myuser:mypassword@123.123.123.123:443 => Will fail https://myuser:mypassword@serv1.myproxydomain.com:443 => Will succeed

Maybe it could be nice to add this information in the README?

3024407779 commented 3 years ago

Do you have a way to set up all page IPs? I need to get all page proxies

CedricBrandt commented 3 years ago

@3024407779 you can set the proxy for the whole puppeteer instance via chromes launch parameters

mhombach commented 3 years ago

I had the same error, when we use a HTTPS proxy, we should use the domain name as host, we can't use an IP address or the security handshake with the proxy will fail.

https://myuser:mypassword@123.123.123.123:443 => Will fail https://myuser:mypassword@serv1.myproxydomain.com:443 => Will succeed

Maybe it could be nice to add this information in the README?

I think this is not the issue. You can, without any problems, start Chrome(Chromium with the proxy-parameter and assign a proxy for HTTPS by providing the IP only. So this has to work. I am getting the same error though, would love to get this fixed.