Apify and Crawlee Official Forum
b
F
A
J
A
WARN CheerioCrawler: Reclaiming failed request back to the list or queue. Detected a session error, rotating session...maxRequestRetries: 0. useSessionPool: false but it did not help.ERROR CheerioCrawler: Request failed and reached maximum retries. RequestError: getaddrinfo ENOTFOUND www.cool-rent.eu so I am not sure what happened in version 3.5.0v3.5.0 (relevant PR here - https://github.com/apify/crawlee/pull/2002). With this new mechanism, proxy and blocking errors are retried by default without increasing the request retry count (instead, they have a separate limit of 10 session retries per request - and after that, the crawl is interrupted as this is a clear telltale sign that something is really wrong with the proxy config).v3.5.0 without proxies processes this correctly by returning the same ENOTFOUND error as 3.3.0 . With proxies, I receive a 502 error (from the proxy server) - however, Crawlee does not recognize this error (which is imho correct behaviour) and the error is processed as a regular 5xx error with errorHandler. Can you please share more details about the proxies (or Apify proxy groups) you have used? Have you used proxies even in the 3.3.0 case? WARN PlaywrightCrawler: Reclaiming failed request back to the list or queue. Detected a session error, rotating session... 2024-01-13T11:13:43.450Z page.goto: net::ERR_TUNNEL_CONNECTION_FAILED at https://cudaops.com/ 2024-01-13T11:13:43.451Z Call log: 2024-01-13T11:13:43.452Z - navigating to "https://cudaops.com/", waiting until "load"