Krydos

The free plan is now back, and better than ever! The Johnny rebuild has been completed and free signups will be opening in about 30 minutes. If you don't already have an account you can signup at https://heliohost.org/signup/ We expect signups to fill pretty quickly, so be ready to click as fast as you can. On May 9th we emailed all of the active Johnny users, and offered them a free trial on Morty to get their websites back online during the rebuild. If you are one of those free users currently on Morty we will be emailing you to ask if you want to stay on Morty or go back to Johnny. If you want to stay on Morty you can use this link https://buy.stripe.com/7sI8wOe4p40y9q0147 to pay $5 which will last about 6 months without overages. If you make a payment let us know so we can make sure it gets applied to your account. If we don't hear back from your we will move you to Johnny automatically in a few days. If you decided not to accept a free trial, you can recreate your Johnny account by going to https://heliohost.org/status/ and entering your email or username. The website will recreate your account for you on the new Johnny server. The new account will be empty so if you want to restore your previous website you'll need to download your backup from https://heliohost.org/backup/ or use a backup that you made yourself. Keep in mind that if your backup is missing anything we may still be able to recover it for you. Just let us know what you're missing, and we can take a look. The new Johnny also has a number of upgrades such as Python 3.14, MariaDB 12.2, PostgreSQL 18.4, etc. If your script isn't working, make sure you're using the correct shebang version. Let us know if you have any questions.

I have added a more recent backup for you. Try downloading your backup from https://heliohost.org/backup/ again. If you'd like to stay on Morty you can also use Stripe to pay. This link will charge $5 USD which would last about 6 months on Morty as long as you don't have any overages. https://buy.stripe.com/7sI8wOe4p40y9q0147 We can also provide a $10 link which lasts about 1 year or a $19 link which would last about 2 years.

@wolstech I just checked the NS records, not the DKIM, SPF, and DMARC records. I didn't realize they were already set up. I just knew I couldn't edit their Cloudflare settings for them. @urbanshed If you're DNS records are already set up try sending a real email (not just the word "test" or a blank email) to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.

This domain is using Cloudflare, so the user has to set up DKIM, SPF, and DMARC themselves. We can only set up email for people who use ns1.heliohost.org and ns2.heliohost.org

Fixed.

The directory /var/www/html/files/c-cloud and all contents have been deleted. If you realize you need something that was inside there, or if I misunderstood what you wanted, I made a backup first and put it in /home/marcomessina/c-cloud.tar.gz for you.

So, Morty and Morty2 are using much newer versions of MariaDB than Tommy. When you went from Morty to Tommy some of your new collation doesn't exist on Tommy's older MariaDB so it wasn't able to create those tables. ERROR 1273 (HY000) at line 766 in file: '/tmp/pmm-ru-udb-dump-yVJTNQ/backup_sqldump_2605201808': Unknown collation: 'utf8mb4_uca1400_ai_ci' We're going to be upgrading Tommy to use the same version of MariaDB as Morty2 as soon as the Johnny rebuild is finished. You've got enough Morty balance now to last probably 2 years with no overages, so it probably won't be an issue again for you. I found 6 databases, and put them in your home folder for you as .sql files. You'll probably need to recreate the database, and then import the .sql file in. Since you're on Morty2 now there shouldn't be any issue with the collation anymore. Let us know if you're still missing anything.

This might help you too

Yeah, that's a lot of emails. Backups 0 MB Emails 728.44 MB Files 245.03 MB Trash 0 MB Logs 23.35 MB PSQL 0 MB MariaDB 0 MB Total 996.82 MB 172K /home/urbanshed.helioho.st/httpdocs 245M /home/urbanshed.helioho.st/urbanshed.in 12K /home/urbanshed.helioho.st/.composer You're at 996 MB out of 1000 MB so you may be able to login quick and start deleting stuff before it goes over the limit again.

Your account was suspended because you exceeded your storage limit. You have 3 options to regain access to your account: You are able to regain access to your account immediately without waiting for an admin by increasing your account's storage space. This storage space upgrade is good for the life of the account, and has no monthly cost. Tell us which files you would like deleted and an admin can delete them for you to get you back under your current storage limit. If you're not sure which files are taking up all of your space an admin can provide a detailed storage space usage report for you. We can also reset your account for you which deletes all files, deletes all settings, and restores your account back to the default state with 0 MB of storage usage.

DNS recreated.

Fixed. The issue is Morty has a newer MariaDB than Tommy, and you created your Wordpress database using a collation that doesn't exist in the older MariaDB on Tommy. After converting your data into a collation that Tommy understands it works fine now.

Since the requested modules were installed, and you didn't answer my question about whether or not you're asking about WSGI control access, I'm going to assume you don't want WSGI control access and this request is complete. If you really do want to have WSGI control access enabled please open a new request.

Closing due to inactivity since there has been no response in this thread for over a week. If you're still having this issue or need help with something else please open a new ticket.

To summarize, yes there are two ways to do a websocket on Tommy. You can set up a reverse proxy with .htaccess on your own, but some software have issues with this method. If that doesn't work for you an admin can set up a Nginx reverse proxy for you. You just need to make sure The process that is going to be listening for websocket requests is already running. Let us know your username. Let us know which domain or subdomain you want to be the websocket. Let us know the port your websocket process is listening on. After we have that information we can set up the Nginx reverse proxy websocket for you.