Portal Home > Knowledgebase > Articles Database > Host Blocking Legit Http Requests
Host Blocking Legit Http Requests
| Posted by sceadugenga, 03-17-2012, 08:46 AM |
| Hey Everyone,
Yesterday, we noticed that all http requests were timing out for sites on one of our hosts. Similar http requests are going through just fine for sites on other hosts.
Unfortunately, our host's tech support is simply blaming the issue on the external servers to which our sites are trying to connect, simply saying they are taking too long to respond, but I really don't think this is the issue. To wit, even the news streams in our Wordpress admin dashboards are timing out.
Could this be some kind of mod_security issue? Perhaps a new rule is blocking legitimate http requests? I am not seeing any specific mod_sec error coming up. Rather, just a message that the request timed out, for example:
Do you guys have any pointers, so I could kinda push the tech guys in the right direction? Any insight from you guys would be much appreciated.
Lead generation is a big part of my business, and right now our web forms aren't displaying at all, since they depend on a REST API call to a third-party server. So we're hurting pretty bad right now, and I've got unhappy clients.
Thanks so much for your help!
|
| Posted by storminternet, 03-17-2012, 10:50 AM |
| Hi,
Two points needs check whether your server is blocking the connections to your other server from which your web site trying to fetch API's or the API server is refusing connections from your server.
It might be possible that there is any firewall active on any of these servers which may block the connections, may be there is any mod_sec rule, any hardware firewall filtering the traffic etc.
Such requests may be filtered in case when there is hotlink protection enabled.
You will have check these possibilities on both servers to fix your issue
Hope this helps you
|
| Posted by quantumphysics, 03-17-2012, 10:51 AM |
| try use curl and not file_get_contents?
|
| Posted by sceadugenga, 03-17-2012, 11:22 AM |
| Thanks for the tips!
We checked and there were no mod_sec errors related to the issue. There were also no firewall issues or changes to the server's hardware since March 1.
Oddly enough, my tech guy realized through looking at the error in Firebug that the site was trying to connect to itself, not the remote server (even though the warning error said different).
So he reverted the Wordpress permalinks to their default, saved everything, then went back to the old permalink format. Voila! The errors have been resolved!
So strange, though. We made no changes to the Wordpress version, and he said there were no database errors. So I have no idea how the issue came about.
|
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
