Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Can't connect to *one* specific site anymore.
So here's the deal:
I have a website that I'm building. Been working on it from home here for the past few weeks. Since last night, I've not been able to connect to it anymore. The same with my web hosting provider - I can't connect to them, either.
I can, however, connect to ANY other site, so my first thought was that my hosting provider was down. They are up and running just fine. Then I discovered that if I connect to my VPN, I can connect to my website and my hosting provider with no problems. Odd, eh?
I've tried resetting my modem manually, resetting it through Cox's website, and had a Cox tech guy do it for me. I've checked my PC for updates and restarted it. I looked for recent windows updates, and there wasn't one at the time I lost connectivity to my site/provider. I've cleared my cache and cookies. I've tried different browsers. My hosting provider tells me that they have had no complaints and that all of their servers have been running fine for days.
Again, I can connect to ANY website, just not mine - UNLESS I connect to a VPN.
Any clues? Guesses? Magic spells?
AMignea
New Contributor
•
Are you running a load balancer? Or proxy by any chance? The ip might of been blacklisted. I would check with your isp to see if normal traffic has been automatically blocked due to the proxy looking malicious - sometimes and usually when they update the server sees and treats the traffic coming from the proxy as individual traffic and automatically blocks it because its trying to call too many pages at once instead of what it is and then sees normal traffic as the server. It basically swaps the two and blocks the ip - your standard tier help person will not know how to check for that and unlist you. I just had the same problem with wpengin and was getting a 502 error. Hope thats it - its simple enough to remedy at least until the next update.
0
0
AMignea
New Contributor
•
Are you running a load balancer? Or proxy by any chance? The ip might of been blacklisted. I would check with your isp to see if normal traffic has been automatically blocked due to the proxy looking malicious - sometimes and usually when they update the server sees and treats the traffic coming from the proxy as individual traffic and automatically blocks it because its trying to call too many pages at once instead of what it is and then sees normal traffic as the server. It basically swaps the two and blocks the ip - your standard tier help person will not know how to check for that and unlist you. I just had the same problem with wpengin and was getting a 502 error. Hope thats it - its simple enough to remedy at least until the next update.
0
0
AMignea
New Contributor
•
Are you running a load balancer? Or proxy by any chance? The ip might of been blacklisted. I would check with your isp to see if normal traffic has been automatically blocked due to the proxy looking malicious - sometimes and usually when they update the server sees and treats the traffic coming from the proxy as individual traffic and automatically blocks it because its trying to call too many pages at once instead of what it is and then sees normal traffic as the server. It basically swaps the two and blocks the ip - your standard tier help person will not know how to check for that and unlist you. I just had the same problem with wpengin and was getting a 502 error. Hope thats it - its simple enough to remedy at least until the next update.
0
0