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.
3 Comments - Last post 27 minutes ago by lostsoul67
23 Comments - Last post 1 hour ago by Carenard
283 Comments - Last post 2 hours ago by pb1
2 Comments - Last post 3 hours ago by adam1224
4 Comments - Last post 4 hours ago by Chris76de
350 Comments - Last post 4 hours ago by madjoki
10 Comments - Last post 7 hours ago by 1312poggerson
110 Comments - Last post 48 seconds ago by DeliberateTaco
995 Comments - Last post 1 minute ago by wigglenose
12 Comments - Last post 3 minutes ago by TheCyberDruid
22 Comments - Last post 9 minutes ago by Tucs
390 Comments - Last post 26 minutes ago by DufWhite
224 Comments - Last post 35 minutes ago by Ev4Gr33n
81 Comments - Last post 1 hour ago by Vasharal
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.