wolstech

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.

Unarchived.

Unarchived.

Unarchived.

Unarchived.

Please check your PMs.

This is not possible in stock Apache. It's just allow or block. There are rate limiting modules available, but we don't support any of them. You can manage block lists in cPanel for specific IPs as well. What is the concern about the traffic? Is it causing performance issues or load you're worried about?

Neat.

Your domain has been reconfigured to use that subdomain

Ricky accounts cannot be restored at the moment because the server is being rebuilt. You can either sign up again on one of the other servers for free, donate and be moved to tommy, or wait until the maintenance is complete so the account can be restored on Ricky.

You're suspended for having more than one account. Users are only allowed one account. Which one do you want to keep?

Yeah, eu.org is another one that's not supported for the same reason. The full list of known bad domains is: any .pp.ua, .eu.org, or .br (country TLS for Brazil), any domain purchased through cloudflare, and any domain purchased through OVH. Pretty much everything else works (though a few things like afraid.org's freeDNS have extra steps involved). I'll get the domain moved over to that subdomain in the morning when I'm at a computer next (should be about 9 hours from now).

If you need it as an addon, create a subdomain of your main domain that will hold that domain, then let me know. I can remove the alias and re-park it on the sub. (An addon is just that internally, an alias parked on a subdomain).

This one is kind of weird. This account didn't actually phish, but the same person created another account that did phish (was caught with a phishing site and a database containing Instagram passwords) and is also banned. Also, that app is a glorified spambot. Finally, our terms of service expressly prohibit users from providing social media marketing services.

These are a known problem domain. Their systems don't follow industry standards. Usually the registrar is supposed to set up, then the host verifies the domain is pointed to them and sets up the domain on the hosting account. These noncompliant ones expect the opposite (host must set up first, but host refuses to set up since its waiting for the domain to set up, meanwhile the domain is waiting for the host to set up...you get the idea), and refuse to advertise name servers that aren't set up for the domain. The only way a user can add these themselves is as a main domain, an admin has to manually add them if you want them as an alias or addon (when we add on our end, the system skips the name server check and just adds it). The system successfully parked (aliased) the domain “anachoreta.pp.ua” on top of the domain “anachor.heliohost.us”. There you go Odds are the registrar will update the records shortly and publish the NS for us now. Please remove the cloudflare records. We are unable to provide support for users using CF since we cannot see or control the DNS records with CF enabled.