wolstech

Krydos can take a look, but the fact your account only existed for about 3 weeks reduces the odds of being able to recover any databases. The ones we have recovered primarily came from older backups or account archives that existed before the crash (such backups are system-created when an account is archived from inactivity, and are often created by an admin when an account is reset). What was the name of the database? Also, do you know the name of any of the tables in that database?

Deleted.

An invite has been sent to create a Morty account. Please click the link and follow the instructions to create a new account. Data that was successfully recovered from your Johnny account can be downloaded from https://heliohost.org/backup/ Note that backups may not be available yet for all accounts, and not all data may have been recoverable (especially databases). If there is something specific you need that you don't have a backup of, let us know exact details of what you're looking for and we can take a second look to see if it can be recovered. If you need domains added, please let us know your new username and the domains you need once you finish creating the Morty account so we can get them set back up for you.

This is a Krydos question...

Flask should be standard, but the others need to be installed. Escalating to Krydos.

An invite has been sent to create a Morty account. Please click the link and follow the instructions to create a new account. Data that was successfully recovered from your Johnny account can be downloaded from https://heliohost.org/backup/ Note that backups may not be available yet for all accounts, and not all data may have been recoverable (especially databases). If there is something specific you need that you don't have a backup of, let us know exact details of what you're looking for and we can take a second look to see if it can be recovered. If you need domains added, please let us know your new username and the domains you need once you finish creating the Morty account so we can get them set back up for you.

The server you're on has failed, so we cannot do an automatic move for you. It would be a manual move (download backup, create new account, and set site up again) Since we are currently offering free trials of Morty accounts while Johnny is down, would you like me to send you a free Morty invite? If you choose not to pay after Johnny is restored, we'll simply move you to Johnny at that time (or if you wish, you can pay for Tommy instead of Morty at that time and we 'll move you from Morty->Tommy). If you still prefer to move to Tommy now, I'll just delete your broken account and you can sign up for Tommy normally. If your site needed Python modules, you'll need to request them again on your new server if they're not already present. You'll need to provide your own copy of any databases you had, as most backups do not contain databases (any that do will contain older versions of them). The files from your account can be downloaded from https://heliohost.org/backup/

An invite has been sent to create a Morty account. Please click the link and follow the instructions to create a new account. Data that was successfully recovered from your Johnny account can be downloaded from https://heliohost.org/backup/ Note that backups may not be available yet for all accounts, and not all data may have been recoverable (especially databases). If there is something specific you need that you don't have a backup of, let us know exact details of what you're looking for and we can take a second look to see if it can be recovered. If you need domains added, please let us know your new username and the domains you need once you finish creating the Morty account so we can get them set back up for you.

No they are not. Python modules you requested be installed (and I think WSGI control if it was enabled) do not carry over. Did you request either of these? If so, you'll need to request them again.

Johnny was down for a bit, and I don't see you in the blacklist. Are you still unable to access it? As for uptime, if you need something with proper uptime, you need a Tommy or Morty account. Johnny is meant to be an unstable test server, so this sort of thing is basically normal for it. Tommy and Morty have much better uptime. (Also, it's normal for the login page to not work when your account's server is down.)

Escalating again to get the right one installed for you.

Copying Krydos's response since you also emailed us about this...

Missing DNS zone fixed. It may take a little while before its available everywhere.

Krydos can install this for you. Escalating.

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.

Fixed missing DNS zones. It may take a little while before everyone can access these again.

Is this for VPS120? Escalating...

High CPU load due to overuse of scheduled tasks.... It looks like whatever readMeter.py is, it is either being run way too frequently, or isn't exiting like it should. There were a ton of those running (not all of them shown, I cut the list down). You may want to both debug this script so it exits properly, and also reduce the frequency of this script so they don't pile up. As for Morty upgrades, you can switch to Morty here: https://heliohost.org/dashboard/move/ Morty has a $1/month fee to keep the account open, and charges you overage fees when you use more than the usual 10000 CPU / 200GB RAM per day. You also do not need to log in every 30 days. Morty accounts are exempt from load and inactivity suspensions as long as money is in your account. If the account runs out of money and you don't top up, the account will just move itself back to Tommy (then be suspended if appropriate). I've turned off the scheduled tasks associated with readMeter and unsuspended you. It may take a little while before you can log in again. 15.56 GB 0 (sd-pam) 13.34 GB 6.35 k /usr/lib/systemd/systemd --user 9.03 GB 393.3 /usr/bin/python3.12 readMeter.py 2.09 GB 30.5 /opt/plesk/php/8.1/bin/php-cgi -c /home/system/goensch.helioho.st/etc/php.ini 842.52 MB 0 /bin/bash /usr/local/psa/admin/sbin/fetch_url http://goensch.helioho.st/cgi-bin/readMeter.py 64.05 MB 2.4 /usr/bin/python3.12 gen_view_sum2.py 46.25 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.LKSmvvgMR7 -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 27.84 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.3bT4WWIhJs -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 27.79 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.sgC9xEhLKV -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 18.49 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.hbm0TpQXkp -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 18.47 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.HMDgYOobQe -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 18.45 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.1y4X23gAxf -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 18.42 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.Y8J6zppewO -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 18.33 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.2215BTfpBG -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 12.30 MB 0.1 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.UpbC21aOiM -w %{http_code} https://goensch.helioho.st/cgi-bin/gen_view_sum2.py 12.29 MB 0.1 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.rjoLn3Es3z -w %{http_code} https://goensch.helioho.st/cgi-bin/gen_view_sum2.py 9.31 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.lJPzbVnH4f -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.30 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.GiQXqfgdE8 -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.30 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.Sy8MQArqvq -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.30 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.kmPR9DuHDL -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.30 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.JlDo5hIOYL -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.30 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.ZTylrM7SEG -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.7PYeddLFhZ -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.HTxn5HKQZT -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.J16EmzBGJl -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.jcZiR6mHwx -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.IOLSKkKqNM -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.mhXsPg61nT -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.LLvSq4WYqw -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.TsOHdN2CrO -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py 9.29 MB 0 /usr/bin/curl -A Plesk (fetch_url utility) -sS -L -k -o /tmp/tmp.We24V8I599 -w %{http_code} http://goensch.helioho.st/cgi-bin/readMeter.py

The second name server was still missing the zone. Should be fixed now. Note that between monday and now, your site was in fact available for many users, it just depended on which name server their system decided to query. If it picked ns1, it worked, if it picked ns2 it did not.

If the domain hasn't been added to your account yet, the folder doesn't exist. What is the name of the domain so that I can add the domain to your account?

The basic process is: Request the domain be added to your account here, wait 2 hours, then change the name servers at your domain registrar to our name servers (ns1.heliohost.org and ns2.heliohost.org). Once the DNS updates propagate, you'll see the site you have hosted on Tommy instead of the site you have at your old hosting company (it can sometimes take a few hours before everyone sees the change, DNS doesn't update instantly). Note that we are not a domain registrar, so you can't handle the actual domain registration through us, only the hosting. If you are using the old hosting company for domain registration as well as hosting, you'll want to transfer the domain to a standalone registrar (we recommend Namecheap), then set the domain to use our name servers in the new registrar's control panel.

Fixed missing DNS zone.

This is normal. The IP address is shared across thousands of websites on the same server as you, so it doesn't know which site to display unless you use the domain name. This is called Server Name Indication (SNI). Accessing your site directly via shared IP address is not supported. If you really need your site to work by entering the IP and not the domain, you would need to purchase a dedicated IP address (or switch to a VPS).

The code itself isn't the cause of your load, it's systemd. Whenever a process is running under a user account (CGI execution, scheduled tasks, sftp, etc.), systemd causes load for that account. That load counts even though the script itself uses next to nothing. The load from systemd is basically directly correlated to the amount of time you have processes running. The more stuff you run (or leave running), the higher it gets. You can even get suspended for load by connecting to sftp and leaving the open connection idle. Looking at what's running, the Python apps and the PHP called via scheduled tasks are likely what's causing systemd to be running for your account. Your load by process: 14.71 GB 0 (sd-pam) 12.37 GB 5.45 k /usr/lib/systemd/systemd --user 6.99 GB 34.7 /opt/plesk/php/5.6/bin/php -f httpdocs/airspace_around_me/web/api/ogn_bridge_control.php 5.46 GB 212 python3 -u ogn_bridge.py 4.73 GB 26 /opt/plesk/php/5.6/bin/php -f httpdocs/airspace_around_me/web/api/collector_control.php 3.07 GB 137.4 python3 -u collector_hosted.py 1.37 GB 41.5 /opt/plesk/php/8.3/bin/php-cgi -c /home/system/ogn.helioho.st/etc/php.ini 45.33 MB 0.4 /opt/plesk/php/8.5/bin/php -f httpdocs/airspace_around_me/web/api/notam_control.php 45.20 MB 0.2 /opt/plesk/php/8.4/bin/php -f httpdocs/ogn_tools/scheduled_daily_postprocessing.php 41.24 MB 2.1 python3 -u notam_collector.py 18.11 MB 0.3 python3 Scripts/puretrack_labelsConverter_json_to_db.py

Closing since this was being handled over in email support which is now working again. https://helionet.org/index/topic/67209-hh546672-is-there-an-alternate-way-to-pay-mortys-19-fee/