wolstech

Whatever you're running was using too much memory. Please reduce your resource usage. If this happens again, you'll be asked to provide more information on how you will stop causing so much load. Unsuspended. It may take a few minutes to start working.

Localhost is best practice for anything running on the server accessing the database. It always works and requires no special permissions. Using tommy.heliohost.org as the SQL hostname for code that's running on Tommy itself is not something we'd generally support (we just say use localhost). If you really want to do that for some reason, you might be able to get that working by adding Tommy's IP to the remote access IP list (or setting it to any host).

We've had issues with those in the past...the main issue I recall is that the CF origin certs are not publicly trusted. They're basically self-signed certificates. I haven't messed with these in a while though. Can you put the pem and the key (if its separate) in your home folder (outside of your web root so it's not public!) so I can take a look when I get minute? We usually just tell people to generate an LE cert with the proxy turned off instead, then turn it on. Non-strict SSL ("SSL Full") is the supported and recommended setting on CF for our service. It should work with an LE certificate installed on our end. "SSL Full (Strict)" might work, but tends to be incompatible because it blocks the connection when the certificate is invalid. Plesk, Lets Encrypt, and our custom logic all expect to be able to call your website via its domain and still reach it in these scenarios. It will keep LE's certificates from renewing (especially if the current one is expired), and can result in your domain being disabled for not being hosted here if it lasts long enough... "Flexible SSL" should be avoided because it is insecure.

FTP wasn't set up on Tommy to support connections via IPv6. The suggestion to use the IP was to force an IPv4 connection, which was known to work, instead of letting your OS decide (based on your pictures it was picking v6). The issue with FTP over IPv6 was fixed earlier today, which is why your original settings now work. please let us know if you need anything else.

Domain added. It can take up to 2 hours to start working.

For the database issues, it sounds like you’re logging into the old server. The domain for the server changed when your account moved, you need to remove the 2 from the URL. It’s now just tommy.heliohost.org. Do not use tommy2.heliohost.org for anything (database, Plesk, etc.) or you will either lose data or see stale data. For Plesk, you should be logging in at https://heliohost.org/login/ anyway. Logging in that way will always get you to the right server even if your account exists on two different ones due to a move and avoid the stale data issue. Both old and new servers use Apache behind nginx. If you want, you can turn Apache off in Plesk and use pure nginx.

Account casjay has been moved to Tommy, upgraded to 6000MB since chmweb had it. The domains from chmweb have been merged into casjay, and the account chmweb has been removed. The domains should work within the next 2 hours. When the move and merge finishes, you should get an email explaining how to configure DNS for the csj.lol domain if you're still using it (the casjay domain will just work on its own since its a free subdomain). Please let us know if you need anything else or if something doesn't work right for you.

You can't install it yourself. The other root admin Krydos has to do this for you.

Ok. You'll likely receive an email about casjay moving to Tommy in a little while. Once casjay moves to Tommy, I'll merge chmweb's domain into it then get rid of chmweb. The result should be casjay on Tommy with both domains hosted on casjay.

Resent.

Do you want this as a subdomain of the domain you already have (a07956.a0795683865.helioho.st), or do you want this to stand alone as a07956.helioho.st?

Should be fixed for you. Give it a little while to propagate and for SSL to set up and you should be good.

It's because your domains are redirecting to use www subdomains. Accounts lose their www subdomain when they get moved due to a known issue, so your domains are redirecting to a nonexistent subdomain and showing errors. I'll fix it shortly for you.

Krydos can cancel this for you.

Can you try entering 65.19.154.90 as the host name instead of tommy.heliohost.org? That will force ipv4. If that doesn't work, can you try another device, and another network connection, such as a cell phone hotspot? Beyond that, I'm not sure what else could be causing this. If the above, don't help, let me know and we can see if Krydos has any other ideas...

Try SFTP on 1373 again now. Your account had an issue internally with its configuration. Also, give FTPS on port 21 a try again using tommy.heliohost.org as the server name if that still doesn't work.

Your accounts have been merged so you have both domains since the domain pruebas.heliohost.us belonged to the account you didn't keep. It can take up to 2 hours to function.

Krydos can install this for you.

Domain added. Please be sure to configure DNS. The domain may take up to 2 hours to function.

You have to use the server name (tommy.heliohost.org) for the host. Using your own domain for FTP or SFTP has known issues and is not recommended. Does it work if you use tommy.heliohost.org as the host?

You're suspended for having more than one account. Users are only allowed to have one account. Which one do you want to keep?

You're suspended for having more than one account. Users are only allowed to have one account. One account can host up to 10 domains. Also, one of the accounts is already active. Do you want to keep the one that's active, or have that one suspended and keep casjay? We can also merge the two accounts together if desired. Do you want us to do that? (Doing so will result in the suspended account being moved to Tommy so it can be merged. Our system does not currently support moving Tommy accounts to Johnny, so we can't go the other way).

This has been changed again, and should take effect in the next two hours. Please note that if you change your PHP version the setting might get removed.

It's high load again, and it's due to the software you're running. WordPress is notorious for high load, especially if certain plug-ins are installed (wordfence, woo commerce, and elementor being the big three common offenders). WordPress is an issue often enough that it has its own page on our wiki: https://wiki.helionet.org/misc/wordpress it's basically the number one cause of load suspensions. For what you want to do, a VPS would be the best choice since removing extensions is not going to be a feasible solution. And it looks like you're using 2 of the 3 the biggest offenders. VPS is a little bit more challenging to administer since it comes with SSH access to a command line instead of a UI (although we can install a control panel like Hestia if preferred), but it has no load limits. If you want to try reducing your load, let me know and I can unsuspend you. You're not hacked this time, it's just the software was too heavy.

Can you try using SFTP on port 1373 instead of FTPS on port 21? That's typically a more reliable, and also more secure, method of connecting.