No need to apologize, this seems like a really big upgrade
Comment has been collapsed.
Thank you Cg, there was a moment there I thought I had been a bad boy! ^ ^
Comment has been collapsed.
thank you so much cg... for the update and for everything!
Comment has been collapsed.
Comment has been collapsed.
Almost got a heart attack when I saw that :D I was like "oh shit, username ban was not enough, I got banned by my IP, what the hell did I do" lol.
Comment has been collapsed.
33 Comments - Last post 1 hour ago by RATT78
3,117 Comments - Last post 3 hours ago by Hunf027
46,847 Comments - Last post 3 hours ago by klingki
29 Comments - Last post 4 hours ago by DeliberateTaco
10 Comments - Last post 5 hours ago by DiabLXIX
45 Comments - Last post 6 hours ago by davidpfarrell
235 Comments - Last post 8 hours ago by PsyKo
13 Comments - Last post 14 minutes ago by HimoGa
26,577 Comments - Last post 15 minutes ago by Seafury
89 Comments - Last post 30 minutes ago by icaio
55 Comments - Last post 58 minutes ago by CheMan39
8,989 Comments - Last post 1 hour ago by Moogal
480 Comments - Last post 1 hour ago by Fluffster
87 Comments - Last post 1 hour ago by CheMan39
If you were visiting the site in the past few hours, you likely noticed a temporary IP block and were unable to access the site. This was a bug related to the recent upgrades to our servers. If you were blocked, it was simply in error, and not your fault.
Our site temporarily blocks IP addresses if they're making too many invalid requests. If you view the attached image, you can see we introduced a load balancer today between the user and our web servers. This caused our database to start incorrectly logging the local IP address of our load balancer as the source of invalid requests, instead of the IP address of the user. When the invalid request limit was reached, the IP address of our load balancer, and all incoming traffic was blocked. The site has been updated in the past hour to fix the bug and to accurately resolve user IP addresses with our new load balancer in place, so everything should be working as expected once again. Sorry about the brief downtime.
Comment has been collapsed.