Failed requests - Session closed 'without receiving a SETTINGS frame' or 'NGHTTP2_REFUSED_STREAM'
Failed requests - Session closed 'without receiving a SETTINGS frame' or 'NGHTTP2_REFUSED_STREAM'
At a glance
The community member is experiencing issues with a CheerioCrawler, where requests are failing due to errors in the title. They are unsure if the issue is related to their setup, the source, or something else. Another community member suggests that the issue may be related to proxies, and that using fresh IP addresses solved the problem, even though the IPs "burn" quickly.
I'm playing around with a CheerioCrawler and I've noticed requests failing due to the errors in the title. I'm wondering if it has something to do with my setup(pretty straight-forward and tested before without issues), the source(had no issue with it before as well) or it's something else that I'm missing. Has anyone faced one or both of these errors before?
The core question is if it happens every time or just once a while. If once a while ,then we usually don't care about it. There are tens of different network errors you can get, sometimes it is just bad luck, but it can also be a part of blocking
