Thanks Yeehaw..... I use Websitesource, I heard back from them at 12am and this is what they said:
"Hello
I was able to find something in the handling for ip **.***.***.** that may have caused or contributed to your issue. Please check again and reply to this ticket if the issue persists."
HIP HIP HURRAY!!!!! They finally fixed it!!!!!!
Thank you Tezgno for your full report on this. I was able to paste the report to them and finally they looked for my ip in the system and found it being blocked.
I can confirm that this problem everyone is having is indeed the hosting service causing the problem. No matter what they're saying... don't give up. If they say it's not them ask to speak with a supervisor until someone listens and checks the right place. Paste Tezgno's report to them:
Tezgno
For those of you who are having this problem, I thought that I would chime in explain what is going on here. First, and foremost, I'm a network engineer who has seen this issue countless times and, surprisingly, the problem is not what a lot of people think it is (although it may seem like it is the case). I'll try to explain this in laymans terms.
First, the issue isn't necessarily the AEBS, although it is apart of the problem. What is actually happening here is that you are being blocked by the site, not the other way around. Specifically, your IP address is being "banned" by the site in question (in some cases, temporarily, in others, more permanently). Issues like these are hard to diagnose because most people troubleshoot the issue by unplugging their router, plugging their computer straight into the modem, and then realizing that the issue is gone. Likewise, many people take their routers (in this case, AEBS) to Apple, plug it in, and it starts to work as well. So, let's break this into two parts and address the problem first and why it is happening.
The Problem:
As stated above, the issue is happening because of your IP address being banned by the site you are trying to visit. The reason why you are being banned is a combination of a couple of things on both the sites' side and your side, creating a "perfect storm" if you will. From the sites side of the house, around 2008, many linux-based servers started receiving updates that included security products that would detect rapid or repeated connection attempts (products such as fail2ban and csf). When these security products detect rapid connection attempts or repeated failures, they either temporarily or permanently ban the IP address in question. By the end of 2009, many popular web hosting services and control panel companies included these products as well (control panel companies such as CPanel). The problem is that many people do not know that these products are installed on their servers, let alone that they are running (larger entities do, but the smaller shops and individual site owners rarely do). From the user side of the house, around 2008, many browsers started to include HTML5 capabilities through optional software (such as Google Gears). By 2009, most browsers in some way, shape, or form, started to support HTML5 with its ability to do intelligent caching and DB storage in the browser itself. And, this is where we have the problem. Modern day browsers, in an attempt to make our browsing experience better, tend to open multiple connections to servers so that we can browse the site. For sites that have multimedia, photos, tons of links, etc, (such as blogs, video or photo sharing sites, etc) this results in your browser opening hundreds of connections at once. The problem with this is that if the server you are accessing has systems such as csf installed and you attempt to open a ton of threads to the page, the result is that the software mistakenly thinks that you are a security problem and bans your IP address from accessing the site. For most software (such as CSF), the ban is temporary, but increases in time the more you are banned. For other software, the ban could be permanent.
Why Changing Routers or Plugging in Directly Works:
The reason why changing routers, plugging in your computer directly to your modem, or even taking in your router back to Apple works is because the minute you do any of those things, your IP address changes. This is because most ISPs link the IP address that you are given to your MAC address. Once the MAC address changes (you changing routers, plugging in directly, etc), your ISP will give you a new IP address. When you plug back in your original router, your ISP will return the IP address that you previously had (in most cases. Sometimes, it will give you a completely new address again).
Why this issue is more common with the AEBS than other routers:
In general, this issue is more common with the AEBS (along with cheaper routers) is because the AEBS (along with cheaper routers) generally do not contain QoS (quality of service) controls. Now, for those of you who are technical, you may note that QoS's purpose isn't about preventing you from being banned. And, that is true. For those of you who are not technical, QoS is a process by which your internet bandwidth is regulated by your router so that higher priority items (such as a VoIP phone or a video game) can have more bandwidth available to them when multiple devices are trying to access the Internet at the same time. The reasons why routers with QoS do not experience this issue as often (if ever) is because one of the things that they do is rate and thread limiting. Because your throughput rate and threads are distributed more evenly (rather than a free for all), chances are you will not experience the issue since products like csf work by detecting uneven or rapid connections.
Conclusion:
So, in conclusion, 99% of the time, you are being blocked on the other end. To solve the issue, you generally will have to contact the site owner to have your IP address unblocked. If you are using AEBS, the best thing to do would be to disconnect your AEBS from your internet connection for 24 hours and then plug it back in (most ISPs will assign you a new IP if you are offline for 24 hours or more). Also, try to limit the number of tabs that you open to the same site. If you are being blocked by your own site (and, your site uses CPanel, which it likely does), go into your CPanel settings (WHM settings) (from another connection, of course), go to CSF, remove the ban on your IP address, and add it to the exclusion list.
