wolstech

Unarchived.

Unarchived.

My response yesterday morning was poorly timed, even I didn’t know that K was planning to finish the server yesterday until the announcement. I’ll get this unarchived for you later tonight when I’m at a computer if someone else doesn’t do it sooner.

Unarchived.

Unarchived.

That account is already active.

Krydos has to do this.

Unblocked as well. He probably tried signing in before we restored it...

Unarchived.

Unarchived.

That just needs to be installed yet. PHP is installed without most of its extensions when a server is rebuilt. What PHP version is this needed for?

Unarchived.

Unarchived.

Unarchived.

Unarchived.

Unarchived.

Per our terms of service, users are only allowed to have one account. You technically should've been suspended when you created all 4 of those, however the system missed you for some reason. Which one do you want to keep? The other 3 will not be restored.

Unarchived.

Unarchived.

Unarchived.

Unarchived.

Unarchived.

This isn't really an option for us because (with exception to Wordpress) many times the load that gets people suspended isn't caused by excessive inbound traffic to an account. Very often it'll be caused by things like broken cron jobs, scripts stuck in infinite loops, or by poorly written continuously running programs (node.js, python discord bots, etc.), which more often than not don't have an incoming connection. That said, you could definitely implement your own code that checks the server load and make your application refuse service with a 508 if you wish. This would be an effective way to help reduce your account's chance of suspension. If your app disables itself and doesn't produce any load beyond spitting out the error and exiting when the server gets busy, you'll lower your chances of suspension drastically (during high load, the server suspends accounts in order with the heaviest users first until load is acceptable again).

Unarchived.

Unarchived.