Jump to content

wolstech

Chief Risk Officer
  • Posts

    19298
  • Joined

  • Last visited

  • Days Won

    766

Posts posted by wolstech

  1. Node has been turned off on your domains and the node modules and cache folders have been removed. You're now sitting around 908MB.

    You should be able to download the backup directly from the backup/restore page in Plesk (there's an arrow on the far right to download). Is the option missing for you?

  2. Application pool should be fixed. I just recycled it and the error went away. The second application is technically the www subdomain. I'm not sure what triggered that error, as every single user has two applications due to www and nobody else had this error. If it happens again, let me know and we can look into it further.

    As for the database, I've added that IP as allowed for mysql in the firewall. Your SQL user is already enabled for remote access to % so shouldn't need to worry about that.

    SQL Server doesn't have an IP restriction, so that should just work if you use it.

  3. Krydos will need to fix these. Very few users actually have extra FTP users, and I suspect they don't move across servers at all (or if they do, they break). If I remember right we removed the functionality for them in Plesk a while back of a security issue (Plesk didn't jail them properly), so when users do need them, they have to be created manually.

    Unmarking as solved.

  4. Your account has been reset, and you'll receive an email shortly with a link to complete the process and create a new account.

    If you need any data from your old account, a backup of your old account may be available at https://heliohost.org/backup/ once the process is complete. Note that if your account was reset due to malware or a Terms of Service violation, a backup of your account will not be created.

  5. I assume you mean the Johnny crash, as that was the most recent crash and your account hasn't been on Tommy since 2019. There is a backup from 2023 available at https://heliohost.org/backup/

    Krydos can also probably recover the contents of your home folder from the time of the crash for you as well, however this will not include databases, which for most users have been unrecoverable. If you did want us to check for database data, we would need to know the names of the tables within the database, and the files you'd receive will be raw ibd/frm files that you'll need to extract the data from.

  6. You have a 255MB backup in your account. The rest of your space is being used as follows. I deleted some of the logs for you, but there simply isn't enough space in your account unless you want me to also delete the backup and/or turn off Node and delete the npm cache.

    If you want to buy more space, you can do so in the dashboard. https://heliohost.org/dashboard/ Otherwise, please let me know what you want removed to bring the space under 1000MB.

    305M    ./public_html
    145M    ./logs
    72K     ./error_docs
    12K     ./.composer
    12K     ./.ssh
    0       ./.trash
    0       ./bin
    0       ./cache
    4.0K    ./etc
    0       ./httpdocs
    36K     ./php
    0       ./public_ftp
    188K    ./ssl
    18M     ./tmp
    0       ./var
    283M    ./gsakola.in
    24K     ./.nodenv
    4.0K    ./.phpenv
    120K    ./.rbenv
    355M    ./.npm
    36M     ./.cache
    1.2G    .

     

  7. Users are only allowed to use the python binaries provided by our server. You may not download and run your own. If you have concerns that something doesn't work, you need to contact support. Trying to modify anything outside your home folder, or creating symlinks to files outside your home folder, will result in a hacking ban. You're sharing a server with several thousand other users. If you want to run custom binaries or access the rest of the server, you need a VPS.

    If you use /tmp, you should not leave your files in /tmp permanently, as doing so can fill /tmp (which will break the server) and can also be seen as evading the disk space limit (we've had users do that before...). If you do store something in /tmp, your code should either move those files into your account or delete them when finished.

    If your account is seen doing this sort of thing again, your account will receive a permanent ban without warning or refund.

    Unsuspended. Your account can take up to 2 hours to function.

  8. No worries. Our support is based in America, and when you made the request it was ~3AM EDT. If you make a request overnight (especially between ~12AM - 6AM EDT) you likely won't get a response for several hours just because we're all asleep. 

    That said, I just went to add these for you and realized your account has already reached its domain limit of 15. If you want to add these domains, you need to buy a second account or remove 2 existing domains first. Do you have any domains you want to remove? If not, you can purchase a second account at https://heliohost.org/morty/ then let me know the username and I can add the domains to that one instead.

     

  9. When domains are added/removed, or when settings like enabling node or switching PHP versions are changed, Apache has to restart to load the new config before it takes effect. Since you are one of several thousand sites on the server, there are always changes like that being made, and people waiting for them.

    If you've ever requested a domain or used some of the options in Plesk and were told it takes "up to 2 hours to take effect", the Apache restart is what you're waiting for.

  10. Requests can take up to 24 hours to receive a response, with the oldest requests worked first. Bumping your topic without waiting at least 24 hours may result in your request taking longer than normal to receive a response.

  11. Looks like you left your FTP sessions open. The load was from systemd, which usually happens when processes are running inside a user account for extended periods (FTP connections left open, overuse of cron, etc.). In your case, there are a bunch of FTP connections listed as other processes, including several that are marked idle, so that's the most likely cause.

×
×
  • Create New...