You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From some test that I did, it seems that there an issue with proxies.
Even I put in the @browser a proxy like scrapoxy that supports many proxy management "http://xxxxxxxxx:xxxxxxxxxx@XX.XXX.XXX.XX:8888" also i tested with zyte "http://xxxxxxxxx:@api.zyte.com:8011" , all the connections it seems that cut because of connection is not private. (see the attachment)
it seems that with proxy there is an issue. I don't know what this happened, but didn't the driver need to have a verify property or having to give the path of custom certificate?
Any help it will be very helpful, because I sent many hours to learn the tools and use it and the most important part is that because I will have it in docker inside my VPS can't risk to have any port ban so need to have some proxy.
The text was updated successfully, but these errors were encountered:
I manage to put in os with certutil the ca to pass from proxy lile scrapoxy and use the certificate. But don't need to have the verify and ca_cert property on the driver?
From some test that I did, it seems that there an issue with proxies.
Even I put in the @browser a proxy like scrapoxy that supports many proxy management "http://xxxxxxxxx:xxxxxxxxxx@XX.XXX.XXX.XX:8888" also i tested with zyte "http://xxxxxxxxx:@api.zyte.com:8011" , all the connections it seems that cut because of connection is not private. (see the attachment)
even if you put
or do the same with zyte certification
and then
it seems that with proxy there is an issue. I don't know what this happened, but didn't the driver need to have a verify property or having to give the path of custom certificate?
Any help it will be very helpful, because I sent many hours to learn the tools and use it and the most important part is that because I will have it in docker inside my VPS can't risk to have any port ban so need to have some proxy.
The text was updated successfully, but these errors were encountered: