Apify Discord Mirror

Updated 5 months ago

netERR_TUNNEL_CONNECTION_FAILED

At a glance

The community member is trying to use a proxy with the Crawlee Playwright-crawler to connect to a page on a non-standard port (444), but is encountering a proxy error. Without a proxy, the page loads fine locally, but on a platform, the community member is getting a timeout, possibly due to a banned AWS IP range.

The community members suggest trying proxies from https://apify.com/mstephen190/proxy-scraper or FREEPROXIES group, but those proxies also timeout. They also try using a country-based IP for the Czech Republic, but that doesn't work either. However, the community member eventually finds that the pages are the same without the port, solving the problem.

One community member suggests that the Apify proxy must have the correct port (8000) specified, while another suggests that the port issue might be related to the proxy chain proxy library, as HTTPS should be over port 443 and the specification may not allow other ports.

Useful resources
I am trying to use proxy with crawlee playwright-crawler to connect to page at non standard port (444) and I am getting this proxy error PlaywrightCrawler: Reclaiming failed request back to the list or queue. page.goto: net::ERR_TUNNEL_CONNECTION_FAILED,
any suggestions?
Without proxy it works fine on local. On platform I get timeout which could be because of banned aws ip range.
A
H
L
6 comments
Quick check if proxies from https://apify.com/mstephen190/proxy-scraper or FREEPROXIES group works for you, if not then access blocked by some advanced bot protection, share sample URL or try to switch to PlayWright
I have shared the sample URL via private message. proxy-scraper got about 40 results but those proxies timeout as well
Lets continue here, pls confirm if country based IP for CZ works at your end
Not even czech residentials works for 444 port. But I have just found out that the pages are the same without that port, so that solves my problem.
I think Apify proxy (if you use that) must have correct port specified (8000)
Sorry, I probably misuderstood you, the port is on the target website? That might be then something with our proxy chain proxy library. HTTPS should be over 443. Not sure if specification allows it to go over other ports
Add a reply
Sign up and join the conversation on Discord