Krydos

Try sending an email to https://www.mail-tester.com/ Post the report here if you don't get a perfect 10/10 and we can help you get any issues fixed.

You need to specify your database name, not the postgresql database.

Remote access enabled.

Thanks for bringing it to our attention.

We're all volunteers here giving away hosting for free out of the goodness of our hearts. Then you come along and cause 5+ minutes of downtime on one of our production servers. You rightfully get suspended for it, but if that's not enough you make a lot of non-sensical comments and go leave a 1 star review. We don't owe you anything. We're a certified charity that helps thousands of people around the world and we were trying to give you an excellent, high quality service that most companies would charge for, but if you can't appreciate that then you don't deserve an account. We turn away hundreds of people each day that would love to have one of our free accounts. I would rather one of them have the space your account is taking up on the server because they will actually appreciate what they are getting.

If the database name and the database user are the same as before the remote access will work after recreating it.

Try dropping and recreating the database.

You'll need a VPS for that https://www.heliohost.org/vps/

This would really only affect regular users, and it would only affect their one account. If they clicked a bad link it could do something they didn't intend to their account. Since it would only affect the one account it wouldn't do much. People set terrible passwords and get their accounts hacked all the time, and that gives the hacker full control over their account. Clicking a strange link would give even less access than that probably. A bigger concern would be if a root admin with access to WHM clicked a suspicious link, but there's only 4 of us and I hope we're all smart enough not to click WHM links from someone we don't know. Only about 10 out of 5000 accounts even use two-factor authentication. It seems like most people wouldn't even care about this one. We don't even use this. We use a custom command line script that I wrote to transfer accounts that definitely isn't vulnerable to html injection. The brute force on two-factor authentication is a little concerning for the few people that actually use it, but like I said it definitely doesn't affect many. I have some other reasons to update cpanel on Tommy before too long so this will probably get fixed soon enough.

Unarchived.

Remote access enabled.

You seem to be under the mistaken impression that someone is maliciously targeting you for some reason. There is no "unreasonable reason". It's pretty simple, you cause a load spike and you get suspended. I think Wolstech, an admin, has been suspended for high load a few times. My personal account almost got suspended once for high load. Jenova, another admin, came really close to getting suspended for high load too. Yashrs, another admin, has been suspended a bunch of times. The system doesn't even take donations into consideration. Even donors can get suspended for high load. No one is immune. The reason we have to suspend people who cause too high of load is because if we don't the uptime ends up being like 20%. If you don't like being suspended, either don't cause load spikes by using a lot of memory in a very small time, or move to Johnny where the system doesn't really suspend anyone.

I was able to look up your donations with your email address. You're on Tommy now.

What is your transaction ID(s)?

Did you get it now?

I also sent an invite before I saw that Byron had already taken care of it. When you send a new invite it invalidates the previous invites so only the last one to arrive will work. Please make sure you check the spam folder, and the promotions tab. Thanks for the donation.

We're still in the process of determining whether we would lose money overall by setting up a new server. It's looking pretty promising though. About 10% of the survey emails have been read that we've sent out, and about 13% of the people who read the email are interested in a new server. That's actually much higher interest rate than we expected.

Yeah, after he realized Flazepe didn't know about his third account he logged into a different forum account and requested it to be unsuspended 9 minutes later hoping to have 2 active accounts. That's why I merged the threads.

Extensions created.

Postgis extension created and remote access enabled.

Thanks for letting us know what the issue was. There you go # dig +noall +answer -x 64.71.153.4 4.153.71.64.in-addr.arpa. 86400 IN CNAME 4.subnet0.153.71.64.in-addr.arpa. 4.subnet0.153.71.64.in-addr.arpa. 14400 IN PTR mail.maicol07.it.

The account devd cannot be unsuspended because you already requested jio. If you would rather suspend jio and unsuspend devd let us know.

Since you were so insistent on keeping your username I put in some extra effort to figure out why cpanel was giving that error. I managed to track down the problematic remnants that were left over from when your account was archived and manually removed them. Now your account unarchived without errors, and without having to change your username.

It can take up to 24 hours for a new domain to get set up with ssl. Your account was created less than 5 hours ago. Let us know if you're still having these issues in 19 hours and we can take a closer look. Please be aware that deleting a domain, and re-adding it, changing your main domain, or anything like that can restart your 24 hour timer.

Remote access enabled.