Krydos

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?

Everything looks fine to me too. It was probably the Wordpress plugin. Now that it's disabled let us know if you continue having issues.

What language are you using?

The way WSGI restart control works is you edit the .wsgi file to restart the app. Since your Django app doesn't work yet, and doesn't have a .wsgi file you still can't restart it. You might want to refer to https://wiki.helionet.org/Converting_an_Existing_Django_App

I have increased your Apache and Nginx timeout from 30 seconds to 5 minutes. Does it work now?

The modules you requested were over 8 GB, and we've had several complaints over the last week that Tommy's Python 3.12 has gotten considerably slower due to these modules. They have been uninstalled, and you'll need to get a VPS for this project https://heliohost.org/vps/

The reason the account didn't move automatically is because instead of using the link to move your account that we gave you, you went to https://heliohost.org/signup/ and tried to create a second account with the same email address as your existing account. Each email address has to be unique so you can't have 2 accounts using the same email address. The correct link to move your account once again is https://heliohost.org/dashboard/move/ but you used the link https://heliohost.org/signup/ to try to create a second account. This has happened several times in the last few weeks so we plan on improving the signup page so if someone tries to create a second account it will ask them if they're trying to move their existing account. Sorry for the confusion on how to move your existing account.

Have you tested this script on your local PC? How long does it take to complete on your home PC?

Try this: cd /home/admin/web/centrewebdesign.com/public_html/ su admin /usr/local/bin/composer require wp-cli/wp-cli

I fixed the permissions for your PHPMyAdmin page. Is it working for you now? https://vps111.heliohost.us/phpmyadmin/

There is no Django app on that domain to grant restart access to yet. Let us know once you have a Django app set up.

Sounds good. I created a full backup which you can download from https://heliohost.org/backup/ if you find you need something from your Tommy account, and then deleted the Tommy account as requested. Let us know if you need help with anything else.

Your VPS is rebuilding with Hestia, and you'll get an email in about 30 minutes when it is done. The email will contain the instructions on how to connect to SSH. For Hestia you'll go to https://vps122.heliohost.us:8083/ and login with the username admin, and the SSH password you chose during signup. Let us know if you run into any other issues.

neutility.store - Should be good to go now. neutility.life - You need to change the NS records. Wrong = ns1.heliohost.us, ns2.heliohost.us. Correct = ns1.heliohost.org, ns2.heliohost.org statecollegeguitarlessons.com - Should be good to go. whatsonyourbrain.com - Should be good to go. wordpresscenter.net - Looks good too. centReWebDesign.com - Good to go.

Since you're using Hestia the config files are located in /home/admin/conf/web/domain.com/ not /etc/nginx/ or /etc/apache2/ or anything. You may not need to edit them though, and keep in mind Hestia may overwrite some of your changes if you edit the wrong files. The file should have a comment at the top with the warning when you try to edit it.

Yeah, he forgot that images don't get sent through these support emails.