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.
291 Comments - Last post 1 minute ago by Proteas
1,665 Comments - Last post 7 minutes ago by MaxLevch
3 Comments - Last post 23 minutes ago by GinotheMan
139 Comments - Last post 1 hour ago by Ewoda
33 Comments - Last post 2 hours ago by doomofdoom
2,879 Comments - Last post 2 hours ago by sfkng
17 Comments - Last post 6 hours ago by lext
967 Comments - Last post 29 minutes ago by Venonat
63 Comments - Last post 31 minutes ago by CaspianRoach
197 Comments - Last post 44 minutes ago by Kingsajz
252 Comments - Last post 1 hour ago by Ev4Gr33n
54 Comments - Last post 1 hour ago by NebraskaJones
1,735 Comments - Last post 1 hour ago by windkit
49 Comments - Last post 2 hours ago by FruitCober
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.