Sn1F3rt

No problem ... If you need help with anything else, let us know!

Please clear your cache. Your Ghost installation has been set up on the website you linked.

Your account was suspended for causing high server load. Now onwards, please try to limit the amount of load you put on the servers. Your account has been unsuspended. If you still see the suspended page, please clear your cache. If you need help figuring out why your account was causing such high load, let us know and we might be able to help.

@wolstech, think you didn't get me. That domain `piontkowski.org` ain't a registered domain. And since she (presumably) thought it's free to have maria.piontkowski.org, she put that down in the domain field while signing up. That domain isn't registered by her, that's the thing.

No problem, if you need help with anything else, just let us know.

Yeah, that is Johnny's IP which is shared by all users unless they buy a dedicated IP. That page will show the Queued page forever, it's not your website.

Your account has been created, however, the domain you're using as main domain - maria.piontkowski.org - isn't registered. You might be under the misconception that you could choose any domain you want, but well you'll have to buy that domain, it isn't free. What's free is a .heliohost.org subdomain, so you can get something like maria-piontkowski.heliohost.org or whatever. You can use the domain change script to change your domain here - http://www.heliohost.org/classic/support/scripts/domain

He's on Tommy. Well, recently Tommy has been experiencing high load. Over the last couple of days, I've had a few Tommy users complaining about Tommy's load. All the more, you're using WordPress. WP isn't recommended here because it is known to cause high server load and that's exactly the reason you're getting 500 Internal Server Errors. Joomla is an alternative CMS, you can consider trying it out.

This support request is being escalated to our root admin.

cPanel automatically issues a DV certificate as soon as you add a domain here after pointing the nameservers to HelioHost.However, this process can take sometime to complete. So if you have just added the domain, wait a few hours for the certificate to be issued.

Yeah you can do that ... If your domain is served by Cloudflare then you automatically get a wildcard SSL for your root domain as well as all subdomains. However, remove the SSL only for the domains served by Cloudflare.

And that's the thing. Both Cloudflare SSL and the SSL installed on Tommy cannot live together. This is because Cloudflare already provides you a Flexible SSL and you do not have any need of installing another one. To solve the issue go ahead and remove the Certificates for that particular subdomain from SSL Wizard in cPanel and it should start working again in a while.

Great to know that! Marking the topic as "Solved"

Your request has been escalated to our Root Admin, Krydos.

Thanks.

Yeah, it's possible using subprocess. Use the example start and stop script provided in this Discord bot tutorial. It essentially does the same job. https://flazepe.gitbook.io/heliohost/tutorials/discord-bot

:-) Just a couple days back.

This support request is being escalated to our root admin.

Your request has been escalated to our root admin, Krydos.

Your request is being escalated to our root admin, Krydos.

Regardless of the error, do you have two accounts - one on Ricky and another on Tommy?

You can just create an A record for the subdomain you need through the DNS Zone Editor and add that. Most services show a requirement for nameserver update but that's actually not needed. Even in cPanel, you can just create an A record for the root domain while having it on Cloudflare (though you have to add the domain first here, and then switch to Cloudflare).

Well, Tommy's been experiencing load spikes. It usually gets fixed itself in a while, is it working now?

@wolstech, I'm afraid the problems aren't fixed. Since today morning there are a fresh group of people reporting issues with Tommy, that's frequent 500 Internal Server Errors on Tommy.

Well I dunno, Tommy seems alright rn. Good if it's fixed.