Krydos

You're right. I tested the reset password page, and it wasn't updating the SFTP password like it should. The password reset page has never reset the forum password though as the forum has it's own password reset function located at https://helionet.org/index/login/ and then click "Forgot your password?" We have discussed adding a checkbox to the https://heliohost.org/reset/ page so people can reset their forum password with one page. The reset page should set your SFTP password correctly now.

Did you wait 2 hours after renewing your account?

If you use our nameservers (ns1.heliohost.org and ns2.heliohost.org), the A record and everything will be updated for you. If you use external DNS, such as Cloudflare, you have to update them manually.

Thanks for the donation. We don't have a transfer system yet, so I made a full backup of your Johnny account, deleted it, and sent you an invite for a 2000 MB Tommy account. If you need anything from your Johnny account you can download the full backup from https://heliohost.org/backup/ and you can use this guide to extract it https://wiki.helionet.org/tutorials/plesk/account-backups Click the link in your email to begin creating your Tommy account.

Try temporarily setting your nameservers to ns1.heliohost.org ns2.heliohost.org and let us know if it starts working. If this fixes it then you'll know that the problem is with your Cloudflare settings.

Your backup cannot be restored directly. You need to extract the backup on your home PC and then upload the portions you need. Here are the instructions on how to extract a backup. https://wiki.helionet.org/tutorials/plesk/account-backups Let us know if you need help.

If you have a Johnny account head over to https://heliohost.org/status/ to get yourself set up on the new, freshly rebuilt server. To recap the recent news, about a month ago we noticed quite a bit of input/output errors on Johnny's filesystem. This was surprising because we have redundant raid arrays, and checks in place to alert us if we need to replace a bad hard drive. Apparently the checks had failed, and the raid array was already pretty much destroyed. After failing to rebuild the array using the July 15th data multiple times we tried rebuilding the raid from a drive that was kicked from the array on March 8th. All of the data from March 8th to July 15th was already gone, but we managed to get people backups from the older data. Any changes or new accounts from March 8th until July 15th will need to be restored from your personal backups that you made yourself. Since Morty was approaching completion we quickly finished that server, and then cloned him to make a new Johnny. Setting up a new Plesk server with all of our customizations and settings is very time consuming, but using the cloning technique we managed to shorten the process to only a few days. All of the Johnny accounts that had backups available have been set into the archived state, so if you want to start using your account all you need to do is go to the https://heliohost.org/status/ and it will guide you through the renewal process. If your account was created after March 8th, there is no backup for you, but you can go to the same https://heliohost.org/status/ page and it will give you the option to recreate your account with the same plan and same storage space as you had before. The account will be as empty as a brand new account always is, and then you can restore whatever personal backups you made. If you're having any issues with getting your account working again, let us know, and we can fix it. We have made a lot of changes already to prevent something like this from happening again in the future. Sorry for the downtime, and thank you for your patience.

The website shows as forbidden because you don't have an index file. An example of index file is something like index.html, index.php, etc. As soon as you add an index file the 403 will go away. For example if you access a file directly it displays without issue http://aftersales.sandicliffe.helioho.st/ServiceHours01.html As far as the timeout with your FTP client, the main IP that we used to use was being targeted for attacks, so we null-routed it and moved everyone to temporary IP addresses. Check your FTP client and if it's trying to connect to 65.19.141.77 change it to the IP address listed at the bottom of the Websites & Domains page. Please don't post your temporary IP publicly as the attacker may be reading these forums.

If you downloaded your backup between 2018-08-18 and 2021-02-09, or if you created your own personal backup, then yes. If you didn't do either of the two options, then you'll need to recreate your website from scratch.

I also wanted to mention that we didn't shutdown your account without warning. Here are some old news posts that you could have read at the time to find out what was going on with your account: https://helionet.org/index/topic/36440-tommy-downtime/ https://helionet.org/index/topic/36478-questions-and-answers/ https://helionet.org/index/topic/36577-backups-available/ Sometimes hardware fails, but we did everything we could to backup your site, and no data was lost in the crash.

It looks like you created your account on 2018-08-18 and we held on to your backup until 2021-02-09. Back in those days we had very little storage space for active accounts so when we would run low on space we would delete old backups with the assumption that the owner of the data would have downloaded it they wanted during the 3 years that it was available. Now that we have a lot more storage space to work with we obviously try to hold onto backups for longer than 3 years because a surprisingly large number of people don't read our terms of service, and forget to make their own backups like we always encourage them to.

Thanks for letting us know. Your new VPS has been powered on, and your old VPS has been deleted. Keep in mind you'll get warnings about the SSH key changing again.

Remote access enabled. host=65.19.154.94 port=5432 username=alamai_admin dbname=alamai_database password=<set in Plesk>

Sounds good. Thanks for letting us know.

Here is the first sentence on the dashboard if your domain hasn't been fully set up yet (that no one ever reads.)

That was one of the fastest load suspensions we've ever seen. Created your account at 2024-08-06 15:23:29 and suspended at 2024-08-06 18:26:17. Wordpress is insane. You can read all about how much we love Wordpress on our wiki https://wiki.helionet.org/misc/wordpress The section at the bottom about how to reduce Wordpress load may be of interest to you.

Since your new VPS and your old VPS use the same IP address they can't be powered on at the same time. Your new VPS has been powered off and your old VPS has been powered on. Please note that when you login to SSH you may get some scary errors about it being a different server than expected. That is normal because it is a different server than you last connected to on that IP. Go ahead and log in and check everything out. If the VPS is working fine you can keep it powered on and we can delete the new VPS. If there's some errors or if you want to upgrade to more modern software make a backup of everything you need, and then we can power off the old VPS, power on the new VPS, and you can restore your files to the new one. Let us know how you would like to proceed.

Glad you got it working. Let us know if you need help with anything else.

Try creating the schema now.

What is the error?

Remote access enabled for the new user you created. host=65.19.154.94 port=5432 username=jimkosloskey_whosis dbname=jimkosloskey_test_mule password=<set in Plesk>

Thanks for letting us know.

You have to create the database through Plesk. You can't create databases through DB-Visualizer because it will only have access to the one database that you requested remote access for.

Are you creating your database through Plesk?

Remote access enabled. host=65.19.154.94 port=5432 username=jimkosloskey_novice dbname=jimkosloskey_test_mule password=<set in Plesk>