wolstech

Whatever you were running was a bit too heavy. Please reduce the usage. You can run cron as often as you need, but keep in mind that cron tasks cause load like everything else. Run them too frequently and you'll just end up suspended again. 10-15 minutes might be fine provided the script you're running isn't too heavy, but if it uses a lot of memory it could be too often. Really depends on the script. Unsuspended. The account can take a few minutes to work again.

High server load most likely. If the server is too busy, Passenger tries to start your app but the server can't finish in time, so it times out and that error appears.

What is your account's username?

I see a working website "TanzilSkills - Professional Learning Platform" when I visit your domain. Is there a specific place you're seeing this?

Subdomain added. The domain can take up to 2 hours to function.

Please check your PMs for information regarding your Lily account.

The name servers you need to use are ns1.heliohost.org and ns2.heliohost.org by the way. Looks like MoneyBroz didn't answer that part.

Sharing a network connection or computer will definitely do this. We generally recommend that if an account is being used for school to use their school email address so we know its an education account (this also helps others in their class avoid the same issue if they happen to also use us). He can change his email address in Plesk. Unsuspended. They might take a little while to work again.

Domain added. You'll need to configure DNS for the domain to point to the IPs shown in Plesk. The domain can take up to 2 hours to function. Yes our server will generate a certificate for you once DNS is configured, or you can issue it manually from Plesk. Note that it can take 2 hours for SSL to work once a certificate is installed. As for moving, you should be able to just download everything from your old host to your computer, then upload it here via either Plesk File Manager or an SFTP connection (use host tommy.heliohost.org, port 1373, protocol SFTP, and your plesk username and password). If you have a lot of files, zipping them will make the transfer much faster because you can upload one file then unzip it in the file manager, vs. uploading 1000s of individual files.

Created. Please be sure to configure DNS by pointing the domain to our name servers or by using A and AAAA records pointed to the IPs shown in Plesk. It can take up to 2 hours to function.

You can do this yourself in Plesk. See https://wiki.helionet.org/Node.js

Glad to see you got it working. Please let us know if you need anything else.

Yeah /tmp is shared by everyone. It's just how Plesk servers work (I know some other products put a user's /tmp inside the home folder which IMO would make more sense, but it is what it is). You shouldn't be able to save things anywhere besides /tmp and ~ though, and there are certain commands, files, and folders that can trigger a permanent ban if their account is seen messing with them. In fact, people tend to fill up /tmp accidentally quite a bit with broken Node apps (passenger logs get saved there, and when people do things like write bad apps, or delete their node app without turning node off, passenger sits there slowly filling /tmp with logs until the server breaks). You'll get suspended for filling /tmp, and monitoring to automatically handle /tmp filling up is a project currently on our radar since its a common issue. We had an outage on Morty due to a full /tmp the other day. As for the space limit not changing in Plesk, consumed disk space is only recalculated a few times a day, so you can technically exceed the limit up front, but it will automatically suspend you when the next recalc happens.

The .well-known folder is a weird folder, I've run into a few different things that behave strangely in there. You'll need to remove the below section (or at least add a second condition that allows access to the acme-challenge folder and anything inside) if you want Lets Encrypt SSL certificates to work properly. # Block directory browsing in .well-known paths RewriteCond %{REQUEST_URI} ^/\.well-known(/openpgpkey(/hu)?)?/?$ RewriteRule ^ - [F,L] Plesk creates things in /.well-known/acme-challenge to verify the domain, so you cannot restrict access to that folder. Some other services you might want to use also need access to .well-known too, so we generally recommend not restricting .well-known at all. Also, be aware the Options line in .htaccess doesn't behave very well on Plesk, so that line may or may not do what you expect. Usually if they're not supported, they're either ignored entirely (why you had directory listings despite Options -Indexes being in there), or will cause a 500 error (which will have a line in the logs saying "Options directive not allowed here").

The supported way to turn off directory listings on our service is to put an empty index.html file in the folder to hide the listing.