#1 ·
I’ve been noticing this weird glitch where the server starts tripping whenever things get busy—usually right around 8 AM, midday, or during that evening rush at 5 or 6 PM. It keeps throwing errors with login requests.
Basically, you log in just fine, but the second you actually try to post something, the forum kicks you out and asks you to log in again. It’s a total loop! You can’t do anything, not even check your DMs. The only way to fix it is to basically walk away from the computer for about 15 minutes, and then somehow it just "fixes itself." It’s incredibly annoying.
It looks like the issue might be tied to those Akamai cache servers that most US internet service providers rely on. If you run a quick netstat, you’ll see this address popping up constantly:
(ip adresa).deploy.static.akamaitechnologies.com:http
Everything only goes back to normal once that connection hits a fin_wait state. Since these are supposed to be cache servers meant to lighten the load, it seems like when the main site gets slammed, the server isn't communicating the connection status properly to the cache servers.
You guys should probably double-check the cache forward protocol settings on your server and make sure everything is syncing up correctly with the ISPs.
Basically, you log in just fine, but the second you actually try to post something, the forum kicks you out and asks you to log in again. It’s a total loop! You can’t do anything, not even check your DMs. The only way to fix it is to basically walk away from the computer for about 15 minutes, and then somehow it just "fixes itself." It’s incredibly annoying.
It looks like the issue might be tied to those Akamai cache servers that most US internet service providers rely on. If you run a quick netstat, you’ll see this address popping up constantly:
(ip adresa).deploy.static.akamaitechnologies.com:http
Everything only goes back to normal once that connection hits a fin_wait state. Since these are supposed to be cache servers meant to lighten the load, it seems like when the main site gets slammed, the server isn't communicating the connection status properly to the cache servers.
You guys should probably double-check the cache forward protocol settings on your server and make sure everything is syncing up correctly with the ISPs.