wolstech

As sohamb03 said, the load keeps spiking and generating 500 errors. It's not even just cPanel that's breaking, the actual websites are going down as well. I'm getting tons of uptime robot emails every day, nearly all for 500 errors on Tommy. It might just be high load due to abuse (DoS wouldn't surprise me considering I banned several phishing sites on Tommy yesterday), but if not, I'm wondering if Tommy is reaching (or over) capacity. You can see the load spikes: http://heliohost.grd.net.pl/monitor/

Done. You should now be able to log in and your website should start working within 2 hours.

Unarchiving.

Unblocked.

Unblocked.

Unblocked.

The suspension is for too many emails, which isn't surprising. You are more than welcome to send such emails, but there's a limit of 50 per day to help keep our servers from getting blacklisted. If you'd like a limit increase, please post an example email and how many you expect to send per day. Normally I'd also ask for email address source and unsubscribe info, but your use doesn't email outside users so is not relevant. Unsuspended.

It's banned for phishing. Why do you have a fake bank website on your account if you are not trying to steal information? There's zero legitimate uses for such a website except maybe a development or test platform, and if that's the case, it should have warnings on it advising users that it's for demonstration only/not a real bank. Please create a new account and don't host that here again.

It's archived but the archive is missing. Krydos usually can somehow restore these. I don't see the file anywhere on either server...

Done. You should now be able to log in and your website should start working within 2 hours.

Unarchiving...

Shebang line is wrong. Perl is here: /usr/bin/perl

What's the shebang line in the CGI file? Also, make sure your file has unix line endings. Windows line endings will cause these errors.

The folder had the wrong owner (was owned by nobody for some reason). Your domain is working now, and I can see the files in file manager now as well http://dopplerdave.info/

That account is now created

The domain tommygun.heliohost.org has been cleaned up. Invite sent. Please check your email for the invite to complete creation of the account. If it fails again, please let me know and I'll have Krydos manually scrub the domain. The killdns script has had issues clearing out domains on a few accounts...

Done. You should now be able to log in and your website should start working within 2 hours.

Unarchiving...

Please check your PMs.

I'll assume he deleted it because no account with that domain exists.

That’s weird... Let’s see what Krydos says. Changing an IP should not cause that error. If it weren’t configured for remote access, it’d be an access denied error, so it’s not that...

I’ll set this up when I’m at a computer later today. You’ll receive a PM with information once set up.

This is usually caused by badly-written code that doesn’t close its connections when it’s done with them. I assume you wrote the program yourself? If so, be sure your code is closing the database connections when you’re finished with them. Many times I find code that opens a new connection for every query, never closes them, and fails when it hits the connection limit. You should either open, query, close every time, or open at the start of the script, reuse the single connection for every query, and close it at the end.

A Whois response and an actual dns response are two separate things. They can say whatever they want on the Whois, but unless dns actually answers with the NS records, it won’t work. Your registrar is probably leaving themselves as authoritative and improperly delegating the domain. Contact them and ask that our NS be made authoritative for the domain and their NS be removed entirely. If they say they can’t, then you’ll need to find a new registrar.

That account is working. http://ubitech.heliohost.org/ Please sign in here: https://tommy.heliohost.org:2083/ instead of using our website. The account record is just missing from one of our systems, so our website won't work for you for the time being. I'll fix that when I'm near a computer.