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.
18 Comments - Last post 9 minutes ago by BlazeHaze
10 Comments - Last post 12 minutes ago by lostsoul67
20 Comments - Last post 28 minutes ago by Zepy
1,538 Comments - Last post 33 minutes ago by xFallenAngel
2,670 Comments - Last post 1 hour ago by MeguminShiro
27 Comments - Last post 1 hour ago by Chris76de
160 Comments - Last post 2 hours ago by MeguminShiro
81 Comments - Last post 7 seconds ago by LycanKai
49 Comments - Last post 1 minute ago by MaxLevch
96 Comments - Last post 2 minutes ago by raydotn
33 Comments - Last post 10 minutes ago by m0r1arty
38 Comments - Last post 10 minutes ago by druminy
67 Comments - Last post 12 minutes ago by nonamebg
64 Comments - Last post 13 minutes ago by Fluffster
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.