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.
2,032 Comments - Last post 3 minutes ago by tap7
17,648 Comments - Last post 8 minutes ago by wendrew100
29 Comments - Last post 26 minutes ago by CRAZY463708
12 Comments - Last post 1 hour ago by BEAUREGARDE
13 Comments - Last post 1 hour ago by BlazeHaze
511 Comments - Last post 1 hour ago by Heitor112
0 Comments - Created 2 hours ago by BlazeHaze
64 Comments - Last post 5 minutes ago by Cassol
2 Comments - Last post 9 minutes ago by PapaSmok
182 Comments - Last post 11 minutes ago by Freilyreydia
638 Comments - Last post 12 minutes ago by Freilyreydia
3 Comments - Last post 29 minutes ago by wormmayhem
72 Comments - Last post 30 minutes ago by Vini1
16 Comments - Last post 37 minutes ago by speks
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.