Krydos

Since the webpage is timing out, I'm wondering if you got blocked in the firewall? There were about 20 IPs that were blocked, and I'm not sure which one is yours so I just deleted them all and restarted the firewall. Are you able to see your websites now?

I tested your SSH account and it works fine for me puspusssh@vps118:~$ which sudo /usr/bin/sudo puspusssh@vps118:~$ sudo su [sudo] password for puspusssh: root@vps118:/home/puspusssh# exit puspusssh@vps118:~$ sudo /usr/local/hestia/bin/v-change-user-password admin newpassword puspusssh@vps118:~$ I didn't leave the password as "newpassword" though because it is very insecure. Which SSH account are you logging in to? I see you have an FTP account too. If you login to that account via SSH it might not have sudo privileges.

Thanks for clarifying. I'll see what I can do. In the meantime change your A record to 65.19.154.78

This VPS was sold 5 days ago so it is no longer available. I'm confused, which control panel do you want installed? Yep, looks good on our end.

In order to login to Hestia first login to SSH using Username: jsabarese Password: <same as the dashboard> and then through SSH run sudo /usr/local/hestia/bin/v-change-user-password admin NEWPASSWORD And then go to the Hestia login page at https://vps111.heliohost.us:8083/login/ Username: admin Password: <what you entered in SSH>

Thanks for noticing that. It looks like Johnny's time sync process stopped, and the time got about two minutes off. Morty, Tommy, and the rest of the servers weren't affected. Johnny's time sync has been started again and the time is correct.

You're doing great! Keep up the good work.

We have to have a physical address listed to be incorporated in the state of Washington, so we use Ashoat's parents house where he was living when he was 14 and started HelioHost. Don't look the address up or send anything weird to his parents. I'm not sure if they even know that HelioHost exists or is still operating from their address. Everyone just volunteers remotely.

Stevie, Charlie, Johnny, and Cody were our first four servers and Ashoat, our founder, just named them himself. No one really knows why he came up with those names and when we asked him he said, "Man, I have no idea. I was like 15 years old so who knows what I was thinking." After that things got a lot more democratic, and we would come up with a list of possible names and vote on them. The only rule is hardware ends with -ie, and virtual machines end with -y. So the next server we bought was named Eddie, and then Tommy. Then we got Katie, and Lily. Next were a fundraiser to buy Sparkie, and Ricky. It was around this time that we thought it would be funny to have a server named Ricky and a server named Morty because of the TV show Rick and Morty so we have been planning on using the name Morty for a while. Ricky is temporarily retired right now because we switched from cPanel to Plesk and never rebuilt Ricky with Plesk yet. After that someone donated a server, and we told him it had to end with -ie and he named it Lucie after his cat who was actually named Lucy, but he was fine with it ending with -ie instead. After that we did another fundraiser to buy a server that we named Annie. I don't think we've decided on a name for the new 2025 fundraiser server, but we're definitely bringing the name Ricky back to hang out with his pal Morty who was released a couple months ago.

No, it's not currently possible for users to reinstall their operating systems themselves. We are planning on granting console access eventually, but things move a little slower around here than a for-profit company because we're all volunteers and just maintain this project in our free time.

Is Python 3.12 working at normal speed now?

I started your VPS rebuilding. You'll get an email in a bit when it finishes.

Would you mind trying Python 3.9? I'm trying to determine if only Python 3.12 is affected, or if it's the whole server. Let me know what modules you need for Python 3.9. https://krydos1.heliohost.org/pyinfo/info3.9.py

We can go ahead and reinstall the OS and Hestia again if you want to start over. While Debian 12 is an operating system we support, we would much rather install Ubuntu 24 for you because installing Ubuntu 24 and Hestia is fully automated, and takes about 30 seconds of work from an admin. Installing Debian 12 and Hestia would require probably about an hour of manual installs. We've been providing VPS services since 2017 and have only had 14 Debian VPS so far, so it probably isn't worth the effort of automating.

It looks like you're trying to edit the files for the domain vps111.heliohost.us. Does it work if you try to edit the files for one of your domains?

Since your website uses an SSL certificate whose root was generated in March 2024, it's possible your phone OS hasn't been updated since then to include the new root certificate. Does SSL work if you run the latest updates?

SPF, DKIM, and DMARC have nothing to do with https. You can have SSL and not have SPF, DKIM, or DMARC, or you can have SPF, DKIM, and DMARC but not have SSL because they don't affect each other. DKIM, SPF, and DMARC have been set up for the domain swflspas.com. We recommend sending a test 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. SSL is still working for me. Here is IPv6: root@control [~]# curl --verbose https://swflspas.com * Trying 2001:470:1:1ee::3004:443... * Connected to swflspas.com (2001:470:1:1ee::3004) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * CAfile: /etc/pki/tls/certs/ca-bundle.crt * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS header, Finished (20): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.2 (OUT), TLS header, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS header, Unknown (23): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 Here is IPv4: root@control [~]# curl -4 --verbose https://swflspas.com * Trying 65.19.154.94:443... * Connected to swflspas.com (65.19.154.94) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * CAfile: /etc/pki/tls/certs/ca-bundle.crt * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS header, Finished (20): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.2 (IN), TLS header, Unknown (23): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.2 (OUT), TLS header, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS header, Unknown (23): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 Here is another SSL tester https://www.sslshopper.com/ssl-checker.html#hostname=swflspas.com

Your VPS is now 12 days overdue. Have you made any progress paying for it?

I recommend using .htaccess to redirect to https since you can exclude the .well-known directory. That will allow SSL to renew automatically without an issue in 2 months. If you enable the https redirect in Plesk you will likely have to disable it again and manually renew your SSL.

Does this help? https://wiki.helionet.org/SSL_Certificate_Problems#Ensure_Redirect_HTTP_to_HTTPS_is_Off

I'm glad you're challenging yourself to remember how to do web design, and it's great to hear that it's going well. We mentioned earlier that we can set up a free something.helioho.st domain for you pointed at your VPS if you want, but you can also use all of your existing paid domains. Your VPS already has Python 3.12 installed if you want to play around with it. You can find the binary at /usr/bin/python3.12

Awesome! Let us know if you run into any other issues.

We recently upgraded the servers to latest software and there appears to be a bug in Plesk. You can see this thread https://talk.plesk.com/threads/internal-errorfailed-to-load-tree-data.377058/post-958164 for details. We'll update Plesk again as soon as they release a version that doesn't have the bug. I doubt it's possible to downgrade the Plesk version.

Does this help? https://stackoverflow.com/a/74737612 Also, I'm guessing the reason it worked with Johnny and not with Morty is because Morty is running a much newer version of MariaDB than Johnny. Visual Basic 2012 is 12 years old so it probably connects to older databases as well. Johnny will be upgraded to the newer version of MariaDB as well eventually.

What is the exact error message?