wolstech

This support request is being escalated to our VPS admins.

Ah that's the issue. I've been looking at your Plesk account since that is was what matches your username mm1. Thanks for clarifying it's the VPS with the issue. Krydos or MoneyBroz will need to take a look at that for you since it's a VPS issue. Escalating.

You have two different accounts, so two different blocks of storage, each of which is managed separately. Specifically you have: 1000MB on Morty Your VPS storage. You have to log into each of these separately depending on where you want the files stored. If you log into mm1 on Morty, you cannot upload files to the VPS using the plesk interface. You can only upload to the Morty storage through Plesk. For the VPS, you'll likely need to upload through an SFTP connection unless a control panel was installed. You don't have a tommy account that I can see. Your Tommy account became a Morty account when you upgraded it.

Removed.

This is not supported. Plesk uses httpdocs instead of www as the document root for the main domain, and renaming it can cause your account to malfunction.

You can't. It's disabled for security reasons on all Plesk plans. If you need access to SSH, you have to buy a VPS instead.

Disk space usage can be seen in Plesk. You just log in and select Account on the left side. The "resources" section on that page will show what you're using overall.

There is no limit on the number of files. The limit is based on storage space. If it fits within your 1000MB quota, you should be able to upload it.

We haven't received any other reports of issues with SFTP on Morty, so this may be a connection issue of some kind. Does it work if you upload via the Plesk file manager? Also, how big is the file? Your account only has about 148MB free (showing 852MB of 1000MB used at the moment).

Alias added. It can take up to 2 hours to function.

Do you plan to redirect one domain to the other, or do you want both domains to work and show the same content?

This looks like it may be a bigger issue with Tommy. I just found what I think may be other accounts that are similarly broken. Escalating to Krydos.

The home directory for this account is completely empty. The httpdocs folder and even the logs folder is missing. A backup dated 2024-09-28 is available for this account. Would you like to restore it?

Unsuspended. It might take a few minutes before you can log in again, and domains can take up to 2 hours to start working.

It's for excessive CPU coming from systemd. Yes leaving FTP connections open continuously will cause it, as can having cron jobs set to run too frequently. This was your load chart over the past 24 hours. Are you ready to fix the issue?

No it should not affect the ability to log into Plesk. If you cannot sign in through https://heliohost.org/login/ , my next suggestion would be to try resetting the password.

Domain changed. It can take 2 hours or more before it works.

You're suspended because WordPress got hacked and your account is full of malware. This is extremely common for Wordpress and is a major reason we recommend avoiding it. Because the account is full of malware, you'll need to reset your account (which deletes your data) and start over. Are you ready to reset your account?

Load is coming from systemd, which is caused by either excessive cron job runs or FTP connections being used heavily or left open for long periods. Another user who had excess load from systemd solved it by reducing the frequency of their cron jobs.

Domain added. Please be sure to configure DNS for the domain. The domain can take up to 2 hours to work.

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

Below is the zone file for your domain. Note that we do not allow external DNS for .helioho.st domains. If you were looking for this information so you could switch DNS providers, you'll need to get a domain that does not end in .helioho.st or .heliohost.us to do that. tanzilskill.helioho.st. IN A 64.62.151.106 tanzilskill.helioho.st. IN AAAA 2001:470:1:1ee::2009 ipv6 IN AAAA 2001:470:1:1ee::2009 tanzilskill.helioho.st. IN MX 0 tanzilskill.helioho.st. mail IN CNAME tanzilskill.helioho.st. www IN CNAME tanzilskill.helioho.st. ftp IN CNAME tanzilskill.helioho.st. webmail IN A 64.62.151.106 webmail IN AAAA 2001:470:1:1ee::2009 tanzilskill.helioho.st. 14400 IN TXT "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all" _dmarc 14400 IN TXT "v=DMARC1; p=quarantine" _domainkey.tanzilskill.helioho.st. 14400 IN TXT "o=-" default._domainkey.tanzilskill.helioho.st. 14400 IN TXT ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApPOa/DOn4YrLa3enxk53aqS92AewBWw1rEKemQhEy0uWcmgTO6acu58zQ0lLWn7UBd/NcdKU48Na+/QZPMjlu4SpnpPb0VPHJp5jbzMmodC7h5EqXotpemlySytYpf0/ihOD08HHSMHaTInxq1XwN8EEMn6yYR/sLGjB2dRTcUSlrLNbgZ+UXgKuWHywo3Kfj" "rGQxTRtHRVZjty1qEBSF/fkmofov6a46DM6JzFYyEM8vnFLp+Ei/5y7FZaZZuz0417G5Z4QLrwekDM9WX32AsEar/taIWiYKTiBXMMMRfqtOEWT823SQZ2ITozakgLugOqQIAlad6hGgN4v5ItFHQIDAQAB;" )

Fixed. So this is a weird one. Composer broke because the composer.json that was loaded in Plesk was deleted (which is why the app folder was set to something in .trash). My guess is git moved the old versions to the trash when it updated them, breaking Composer. I had to manually run a command as root to re-register httpdocs as the app folder for your composer, then switch it back for you in the UI. The old broken folders are still going to show as options as there is actually no way to remove them from the system short of manually editing composer's database. It now shows 2 up to date dependencies and 1 not installed. If this is being caused by git deleting the composer.json, the unorthodox solution of committing the vendor folder to the git may very well be the best solution...

Do you mean you want to see what entries are in the DNS zone for your domain? Or do you want us to add specific records (and if so, what do you want added?)

Plesk calls the document root of the main domain httpdocs, but it does the same thing as the www folder on other services. We typically avoid renaming this because it can cause issues with the account. The name of the default docroot tends to vary depending on the control panel and server configurations. Other control panels call it things like www, htdocs, or public_html.