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.
1,925 Comments - Last post 1 minute ago by zand
4 Comments - Last post 9 minutes ago by GraVe23
18,750 Comments - Last post 1 hour ago by MeguminShiro
5,909 Comments - Last post 1 hour ago by K1R4D3L
2,199 Comments - Last post 1 hour ago by Lugum
125 Comments - Last post 6 hours ago by antoniogmad
9 Comments - Last post 9 hours ago by 86maylin
10,403 Comments - Last post 10 minutes ago by hbarkas
1,241 Comments - Last post 29 minutes ago by gus09
435 Comments - Last post 32 minutes ago by quinnix
46 Comments - Last post 39 minutes ago by orono
33,140 Comments - Last post 41 minutes ago by ManOman
322 Comments - Last post 1 hour ago by wigglenose
154 Comments - Last post 1 hour ago by Gortus
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.