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.
15 Comments - Last post 12 minutes ago by Sundance85
3 Comments - Last post 2 hours ago by trunks10k
359 Comments - Last post 4 hours ago by SirChrisSwan
39 Comments - Last post 6 hours ago by Massulan
50 Comments - Last post 6 hours ago by wigglenose
27 Comments - Last post 7 hours ago by Foxhack
17 Comments - Last post 7 hours ago by sensualshakti
40 Comments - Last post 1 minute ago by Devirk
407 Comments - Last post 15 minutes ago by MountainWulf
204 Comments - Last post 45 minutes ago by squall831
743 Comments - Last post 1 hour ago by cocoiv
31 Comments - Last post 1 hour ago by httrenard
3 Comments - Last post 1 hour ago by Mhol1071
21 Comments - Last post 1 hour ago by UnknownEAK
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.