wolstech

Krydos will likely need to check the firewall to resolve this as DmC described. Escalating.

Send me a PM and I’ll pass it along to him in a staff channel.

The issues you described are known side effects of the repair and are things you have to fix yourself. Try the guides linked in this news post.

The Tommy server is currently undergoing maintenance due to an issue encountered late last night. Your account will finish creating once the server is working again. We expect the maintenance to be completed and your account to create within the next hour or so.

The website login and database server are working again. Apache isn't working properly yet though. Still showing a config error in the backend of Plesk, and because of the issues the scheduled 2 hour restarts (and all other maintenance functions like account creates and inactivity suspensions) are stopped, so changes are not going into effect.

The API needed for the HelioHost Dashboard still isn't working, and it looks like all SSL certificates were disabled internally again (the repair tool does this as part of a repair, users have to remove and reinstall them to fix it). I reinstalled your cert for you, but until the server is fixed completely and bihourly is running again so Apache restarts, it's not going to take effect.

That's normal unless you request SPF and DKIM be set up. DKIM, SPF, and DMARC have been set up for the domain rsd.helioho.st. We recommend sending a test email to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be. The missing webmail cert should fix itself in the next few hours. If it does not, try reissuing the cert manually. As a reminder, there is a sending limit of 50 emails per day. Exceeding this limit will result in the removal of email service from your account.

Apache is/was broken on Tommy. As of last update, a repair task was running on Tommy. That incident auto-resolved because the server is responding again, however it's still not 100% and some things aren't running properly yet. Once it's fixed completely, you'll need to remove and reinstall the certificates and wait 2 hours (the repair tool deactivates all certificates internally, which is why your certs aren't working).

Looks to be VPS33...Krydos can cancel this for you. Escalating.

Tommy had a bunch of issues last night. Apache is (was?) broken, among other things. This is part of an ongoing issue on Tommy.

It looks like your renewal failed and it stalled bihourly (the master script that processes jobs on the hosting servers). Krydos will need to fix it.

Krydos can assist with this.

DKIM, SPF, and DMARC have been set up for the domain gebu8f.link. We recommend sending a test email to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be. Please keep in mind also that there is a sending limit of 50 emails per day and 10 emails per hour to prevent spam. Exceeding the 50/day limit will result in email service being removed from your account.

Yeah, the www record was indeed missing. It's been fixed and the cert has issued successfully.

Your account has been reset. You should receive an email shortly with a link to finish the reset process. If you need anything from the old account, a backup can be downloaded from https://heliohost.org/backup/

Sure. Escalating.

Flask cannot be installed on Python 3.9 because it would conflict with the version installed on 3.12.

Added. Please be sure to configure DNS. The domain can take up to 2 hours to work.

Deleted. Thank you for using HelioHost. Please note that our system doesn't store any bank information. All we receive is a transaction number and the amount of your payment from Paypal when you pay, which we use to determine how much you paid and what size account to assign. Paypal stores the actual bank information on their end in your Paypal account, and HelioHost does not have access to that data.

Krydos would need to open this. In the meantime, is it possible to have the remote end reconfigured to be accessible over a port that’s already open like 3306?

Glad to hear its working for you now Please let us know if you need anything else.

Unsuspended. Please fix the issue quickly. Also, I've put deny from all in your .htaccess to keep it offline so it cannot be attacked until you can fix it. Please remove this line once the issue is resolved. If this happens again, another unsuspension might come with the requirement that you eliminate Wordpress.

Your Wordpress install got attacked by bots and basically broke Johnny due to load. This was Johnny's response time while your site was active (the spikes to the top of the chart were the server timing out), and I've also attached a picture of a traffic log. Your site being attacked repeatedly caused intermittent downtime for ~2000 other websites. This is why we say not to use Wordpress. How do you plan to fix this?

We blocked the site intentionally to keep you from being suspended because it was being attacked or otherwise malfunctioning. That cliff is where we disabled your website for you. You were at over 9800 CPU and quickly approaching the limit of 10000. It was either "block the site and keep the account active" or "get suspended for high load". We decided to block the attacked site for you so you could at least keep using the rest of the account. If you want to unblock the site, you can remove the deny from all in your .htaccess file. In many cases we've just blocked bots and such specifically for users, and you would never notice anything, but since your site uses CF, we only see CF's proxy IPs, not where the attack is coming from, and so had to block everything.

Changed. It can take up to 2 hours to take effect.