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.
Almost got a heart attack when I saw that :D I was like "oh shit, username ban was not enough, I got banned by my IP, what the hell did I do" lol.
Comment has been collapsed.
18 Comments - Last post 5 minutes ago by Ellendyl
625 Comments - Last post 11 minutes ago by BlazeHaze
80 Comments - Last post 28 minutes ago by PaganFears
1,527 Comments - Last post 1 hour ago by FranckCastle
18 Comments - Last post 2 hours ago by Dandey
92 Comments - Last post 3 hours ago by anditsung
888 Comments - Last post 4 hours ago by sensualshakti
87 Comments - Last post 40 seconds ago by Whoosh
334 Comments - Last post 1 minute ago by ConanOLion
32 Comments - Last post 7 minutes ago by xandyvan
5 Comments - Last post 7 minutes ago by MarvashMagalli
1,634 Comments - Last post 9 minutes ago by mourinhos86
88 Comments - Last post 9 minutes ago by Venonat
27 Comments - Last post 21 minutes ago by Raggart
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.