wolstech

Plesk only gives us one option that controls all of these features together, turning on the ability for users to change document roots also requires us to turn on the ability to add and edit domains and DNS, which we don't want to allow just yet because it's not finished being developed.

Uptime robot is the monitoring service that I use. It's free for basic monitoring and can be set to send an email whenever something it monitors is down. It can monitor websites or ports, so you can point it at your website or at your SSH port. As for hestia not updating anymore, that's a Krydos question...

Your account looks like a new account made on September 30, not a migration, so you're not supposed to see any old data (this can happen for a bunch of reasons, the most common your old account was archived when our licenses were revoked, you were on Johnny, or you requested a new account instead of a migration). You can use your old account's username to obtain the data from it at https://heliohost.org/backup/ You'll need to download the files in your backup, unpack them, and manually restore the content using the files and database dumps inside. No comment on Wordpress as I generally recommend people not use Wordpress. It hasn't been much of a problem yet on Plesk, but back in the cPanel days it was one of the leading causes of suspension (it loves to cause high load, and is also easily hacked if you install dubious extensions or its not kept up to date...)

Kairion pretty much answered it. SSH is a VPS only offering. If you're on the shared hosting, you're limited to Plesk and (S)FTP.

DKIM public keys are stored in normal TXT records. To enable it, in Plesk, you go to: Mail->Mail Settings->(domain)->Use DKIM Spam protection system to sign outgoing messages->Apply. After that, refresh the settings page and click the "How to configure external DNS" next to the option to see the public key and DNS record you need to create.

Java is not available on our free offerings at the moment due to the recent switch from cPanel to Plesk, but it is one of our most requested features and is on our list of things to get re-implemented. We used to offer it on cPanel, but when we were forced to switch to Plesk, we haven't yet gotten it working with the new platform. Our focus recently has been getting the Johnny server working again so we can finish moving all of the users over to the new system. Once that's done we'll be working more on feature enhancements along with a paid offering called Morty. For the moment, if you need Java, you'll need to buy a VPS instead (please note that there's a waitlist for VPSes right now). If you're interested in being added to the waitlist, you can visit https://heliohost.org/vps/ to sign up.

Domain changed. It may take up to 2 hours for the changes to take effect. In the meantime, please make sure you have an A record pointed to 65.19.141.77 set in cloudflare for this domain.

You can get a Tommy account now if you become a donor (https://heliohost.org/tommy/), otherwise yes, you'll need to wait for Johnny to be finished to get an account and reupload the site from your backup. As for the domain, yes its possible to keep your domain, but you'll need to reach out to us once you have an account again to manually get the domain set back to that because the sign up system won't offer the heliohost.org domains any longer (we only offer .helioho.st and .heliohost.us to new users, but existing users who had one can keep their old .heliohost.org if they ask).

Were you on the Johnny server? If so, that server was hacked and all of the accounts were turned into phishing sites, so we turned that server off. Since it was running cPanel anyway, the entire server has since been wiped and is being rebuilt with Plesk. A backup of your website's files from July 2021 (which would be prior that hack occurring) can be obtained from here: https://heliohost.org/backup/

This might be normal since load is up at the moment, but it's the first time I've seen accounts stacking for hours like this with the server actually up. Krydos needs to look at this as you're not the only one showing an account stuck in the queue...I see 3 sitting in there right now. As for refunds, that's also K's decision since I don't know where we stand on donation refunds policy-wise and he handles much of the money side of things. I've seen VPSes refunded, but that's a paid service, not a donation. I'm not sure where we stand on donation refunds since the Paypal fees cause us to lose more than just the donation itself if we refund it. Please keep in mind that if we do refund it, the account created by the donation will be deleted. EDIT: Of course as soon as I post, the server created the account. It was just load I guess...still need to know on the refund though...

Resent to gmail address. Thank you for the donation.

Probably a bug...Krydos can take a look at it.

Let's have Krydos take a look.

The 2 .org domains on your account are working properly for me. What domain is showing as suspended? I do see bijurs.heliohost.org showing an apache default page, but that's pretty normal when there's no content uploaded for the domain.

Sun Dark linked the TOS which explains all of it, but as long as the content isn't offensive (e.g. hate material/bullying/discrimination/similar material that most would find inappropriate or in poor taste), adult (e.g. porn, nudity, etc.), illegal (e.g. phishing, warez, malware distribution, promoting terrorism or violence, etc.), or abusive (social media marketing sites, bulk email tools or spam bots, etc.) it's usually fine.

The reverse DNS record for tommy is missing according to that error (kind of weird considering mail was working and I can see the record if I query for it but I suppose it's possible it disappeared with the recent IP changes we've been doing on Tommy to help with DDoS). The PTR does seem to exist, so not sure why gmail didn't see it: > set type=ptr > 65.19.141.77 Server: [8.8.8.8] Address: 8.8.8.8 Non-authoritative answer: 77.141.19.65.in-addr.arpa canonical name = 77.subnet72.141.19.65.in-addr.arpa 77.subnet72.141.19.65.in-addr.arpa name = tommy2.heliohost.org >

That's weird...almost looks like your FTP base folder is wrong...escalating to Krydos.

Yes that process requires time. Specifically, Apache has to restart after the certificate is updated. That can take up to two hours.

The above post pretty much nailed it. They likely have no idea who we are, but rather are unhappy with some random user's website. They just look up the IP of the server hosting the site and launch the attack at that. Because of the way our servers work and the type of attack they're using, we have no way of knowing which website/user they don't like because the server IP is shared by everyone. We've been hit before, sometimes repeatedly, but this one is getting ridiculous. While this one probably isn't (at least not on our part), a lot of the DDoS attacks we see here are retaliation of some form. I know of at least one case where someone donated for an account, almost immediately got banned without a refund or replacement because they used the account to set up a phishing site, then DDoS'd us when they lost their money.

Not blocked. Odds are the server was just down again. We are experiencing frequent DDoS attacks which are knocking Tommy offline for a few hours at a time.

We don't support wildcard certiticates at the moment. Uncheck the option for wildcard certificate and try again.

The server is down, probably due to a DoS attack considering we've been hit with a few of those lately...

Krydos has to manually change the DNS to fix this. When this happens, it won't fix itself. A lot of our users have been using external DNS like Cloudflare instead of our DNS because it allows them to manage it themselves. I'll escalate this for Krydos to fix, but if you want to fix it yourself, you could switch your DNS to Cloudflare and set up the entries needed. The records you need in your domain's DNS zone for Plesk to work are: A record pointed to 65.19.141.77 MX pointed to tommy2.heliohost.org (if you plan to receive mail at your domain using Plesk) TXT record with the value "v=spf1 a mx ~all" for SPF (if you plan to send mail from the domain using Plesk).

That documentation is for the old cPanel servers and is obsolete. That said, the script itself should work if you make the script using the below shebang line (we updated Python) in Plesk's file manager. #!/usr/bin/python3.10

This is normal. Users are subject to being pushed back for a combination of reasons, notably if the invites don't go out one day for some reason, or if users donate to skip the queue. This is why we give an estimated time, not an exact one. If a user who was in line behind you donates enough, they immediately move them to the front of the line.