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.
26 Comments - Last post 15 seconds ago by cowbell
625 Comments - Last post 35 seconds ago by IronKnightAquila
3,403 Comments - Last post 5 minutes ago by vlbastos
17,413 Comments - Last post 52 minutes ago by MeguminShiro
47,484 Comments - Last post 2 hours ago by Axelflox
217 Comments - Last post 2 hours ago by RePlayBe
20 Comments - Last post 2 hours ago by pandakat
24 Comments - Last post 1 minute ago by R3size
5 Comments - Last post 1 hour ago by RePlayBe
2,087 Comments - Last post 1 hour ago by patrickmaher
460 Comments - Last post 1 hour ago by shadowshiv
1,304 Comments - Last post 2 hours ago by Eremeir
34 Comments - Last post 3 hours ago by zeruel132
152 Comments - Last post 4 hours ago by ReynardTheFox
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.