wolstech

Did you update your remote database clients to use morty.heliohost.org as the host name? If you're still pointing the clients to Tommy, you'll experience this exact issue. You may also want to try turning the remote access off and on again for the database user. As for the Python issues, I have no idea on that one. The error makes me think something related to WSGI may have broken during the move. Krydos would need to figure that out. As a reminder, it is Easter today, so support is limited. It is possible you won't receive a response until tomorrow regarding these issues due to the holiday.

You need to write a CGI script in a language like perl or python to run the git commands. Then you would use curl in the deploy actions to call the script via http. The curl call will trigger the CGI script, which will cause Apache to run the handler for the cgi, which will in turn run your git commands outside of the jail. Assuming you use Python to make the CGI script, you end up with a flow that looks like: Git Plesk Deploy calls curl->curl request to .py file->apache receives request and calls Python to process script->Python calls git->git processes submodules.

Note that domains that do not end in .heliohost.us or .helioho.st have to be purchased from a registrar. The two domains you mentioned are both for sale, so you don't own them. They wouldn't work if we just changed the domain on your account.

The deployment actions are jailed to your home folder. Since git's binaries don't live in your home folder, it can't find the binary. There is a workaround for this limitation involving CGI that can be tried. Here's a link to another case where a user used that workaround to run npm for a node app, you should be able to adapt it to run git commands instead. https://helionet.org/index/topic/63231-run-npm-script-in-git-deploy-actions/ Note that the "create a scheduled task and run it at lease once" step that I mentioned in one of my replies over is essential. It won't work if you don't do that first (you'll get an error that curl isn't found).

I just realized that was a subdomain. You can ignore the www certs for the subdomains. That behavior is expected since subdomains do not have a www subdomain to secure.

Plesk doesn't let you remove the main domain of an account, it can only be changed to something else. We also cannot convert an add-on domain into a main domain without deleting the add on domain and all of the subdomains, and then setting it all up again (which will also delete all of your data). If you don't want to use that free subdomain, your best course of action would be to just disable it in plesk and ignore it. I'll take a look at the WWW not getting an SSL certificate shortly...

You're welcome Please let us know if you need anything else.

The 502 errors are likely Apache restarting on the server. That happens every 2 hours and is normal.

See https://helionet.org/index/topic/64187-cant-login-after-a-incident-read-description/#findComment-288858

The www subdomain www.coyota.net should work automatically once the name server changes propagate. It is not standard practice to put www before a subdomain (things like www.web.coyota.net should not be used), so that's not supported. It's technically possible to make it work, but doing this will actually hurt your domain's search rankings due to duplicate results, also use up additional domain slots on your account for the aliases (users are limited to 10 domains, you're using 4 now, you'll be using 6 if we added www aliases to the subs), and impact server performance for everyone on Johnny.

If you set the domain to use our name servers at your registrar, we handle all other DNS configuration for you. The WWW subdomain is built in and requires no configuration at all. At the registrar where you bought the domain, you need to set your domain to use custom name servers, and enter ns1.heliohost.org and ns2.heliohost.org as the name servers to use. Be sure our name servers are the only servers specified (you should delete any default ones they provide). Then you wait 24-48 hours for everything to update. Testing on my side shows that a service called spaceship.net is returning for some locations instead of heliohost: https://www.whatsmydns.net/#NS/coyota.net (a domain that is configured correctly and has propagated properly will show ns1.heliohost.org and ns2.heliohost.org for all locations).

I'm not sure what the correct settings are for thunderbird honestly (I don't use it). My guess though is that the authentication method or security option is incorrect (if StartTLS is an option, try that). If you click the advanced config option, is there a checkbox for SPA (Secure Password Authentication)? The host and port are correct. You can also use the email address via the built-in webmail client: https://webmail.tenkyuu.dev/ (use the email address and its password to sign in, not your plesk credentials).

The www automatically exists on a domain and shows the same content as the root domain. There is no need to add anything, it should just work (assuming you're using our DNS). If you use external DNS, you just need to create a CNAME record called www and point it to your domain. As for being unable to log in, try resetting your password: https://heliohost.org/reset/

You're welcome If you want to confirm the SPF and DKIM are working, you can try https://www.mail-tester.com/ Note that if you do this, you should send a real email to it (not just "Test"). If you send "Test" or similar, it'll give inaccurate results (it will likely show a PYZOR check failure and a spamassassin detection).

If you edit the target value of those DNS records to be johnny.heliohost.org instead of your domain, the autoconfig feature should work (no guarantees though, I'm not sure anyone has ever actually tried this before...) You also need to create a few other records: An MX record with a target of johnny.heliohost.org so you can receive mail. A TXT record for SPF. Create a TXT record with a blank name (or you may need to enter your domain as the name), and put this as the value: "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all" A TXT record for DKIM. Create a TXT record called default._domainkey.tenkyuu.dev and put the below value in it: "v=DKIM1; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+SDLc/Hl5PNixlC3Z1QqVI5F0WQUTC0wA2GHBtcHm+cqyRxqCWP7OmmV5Z7Vn3nos10c8TB7chpdkPiTVeO53mrpK6ZC9fjhlfFajdLReXJvRhqR+MBCwUEw1IimwFUz35YIRwqJ2bHaqvtjhuH4oOZ45qq79GB9gsc5OGC/A74pvZBOzMt1zYo3BvwUNo2LTgcyMDTunY+ZU15PBFyE34tj8iniPctiznyx+MboWzR4FCG/igoSwuksUm591bW8PblllmtUzdIQi7ORn9P+JO+bCW29gJlJ77wxupzvelwUMbi/iNWrCnyVbJVNxHxGQTu4jzvMg74BfIGZ1YErmQIDAQAB;"

You should set up the client manually, do not use autoconfig. When entering the connection info, enter johnny.heliohost.org (not your domain!) as the server address. If you enter your domain as the server in a mail client, it will not work. If you want the auto config to work, change the domain name in the target of those SRV records to johnny.heliohost.org as well. Also, did you create an MX record? You need to create an MX record pointed to Johnny.heliohost.org so you can actually receive mail. If you plan to send it, you also need to create TXT records for SPF and DKIM.

Strict mode is a known issue. The recommended settings are Full (but not strict). Plaske is unable to issue certificates when strict mode is enabled because Lets Encrypt requires a plain HTTP connection to verify the domain. This is especially problematic when the current certificate is already expired, or is missing, as Cloudflare will block all traffic to the site if the certificate is invalid, including plain HTTP. Some features such as "keep domain secured" will not function properly with strict mode enabled.

Please clear your cache. The domain is working for me.

DKIM, SPF, and DMARC have been set up for the domain e.killallchickens.org. We recommend sending a real email (not just the word "test") 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 is a quirk of old migrated forum accounts. When a person signs in and checks them for the first time after the upgrade, they instantly get all of the badges they would've earned according to their registration date. That's how you learned all of those "one minute ago".

Domains added. Please make sure you configure DNS. The domains can take up to two hours to work.

It was archived, not suspended. I've renewed your account for you, it may take up to 2 hours to work again. In the future, you can renew it yourself using https://heliohost.org/renew/

MariaDB cannot be updated without rebuilding the server. That said, Morty has a much newer version than Johnny and Tommy because he was built later. You'll need to either move to Morty or purchase a VPS for this. We eventually plan to rebuild Johnny and Tommy with the newer version, but no ETA on this happening. Account xcrow has been reset as requested. An email should be sent shortly with instructions for completing the reset process. If you need the content of your old account, a backup is available at https://heliohost.org/backup/

Krydos can enable this for you

Domain added. We can't enable WSGI control until a flask app is installed on the domain (the wsgi file has to exist before we can enable it), so you'll need to install an app first (it can be anything, even a hello world app, as long as it exists). The domain will take up to 2 hours to start working.