TAS_KEN
Reputation: 13
Facebook Scraper: COULDNT_CONNECT to fwdproxy port 8082
Im surprised to see Facebook did not scrape my website for a while and debugging shows an error
COULDNT_CONNECT Failed to connect to fwdproxy port 8082: Connection refused
Why all of sudden Facebook scraper changed their request to port 8082 ? Or is that normal ?
The port 8082 was never open and all those 6 months fb scraped without any issues and while I was trying to find out what happened this time, that issue resolved automatically. I guess fb changed reqest to 80 or 443
Any idea please ?
Upvotes: 1
Views: 644
Answers (1)
ChiHang
Reputation: 136
According to Facebook Platform Status, there is a Disruption across Platform & APIs on 6th Jun which webhooks are affected. I encountered this issue last week with the same error message. It should be resolved now.
Upvotes: 0
Related Questions
- Facebook Object Debugger - Could not resolve the hostname into a valid IP address
- FacebookAds\Exception\Exception: Connection timed out after 10000 milliseconds
- Unable to scrape website: URL returned a bad HTTP response code
- cURL throws an exception at Facebook API SDK
- URLError: <urlopen error [Errno 104] Connection reset by peer>
- Facebook scraper doesn't work after disabling SSLv3 (sslv3 alert handshake failure)
- Facebook Debugger returns 404 but curl works
- Fatal error: Uncaught CurlException: 28: connect() timed out?
- Uncaught CurlException: 7: Failed to connect
- how to fix a facebook Fatal error: Uncaught CurlException problem