wolstech

Domain added. Please be sure to configure DNS by either using our name servers (ns1.heliohost.org and ns2.heliohost.org) or by using A and AAAA records pointed to the IPs shown in Plesk. The domain may take up to 2 hours to start working.

Your logs are mostly 503 errors, which is due to an ongoing issue involving high volumes of traffic against our webmail service. We're working on mitigating that now. Note that this is different from 502 bad gateway, which is normal when Apache is restarting on the server. That happens approximately every 2 hours and usually lasts 5-10 minutes on Johnny. It's faster on Tommy, and currently doesn't happen at all on Morty due to newer hardware and having so few users and domains on Morty. Static pages will always be fastest because there's no server side scripting, and will typically not be affected by 503 errors. InfinityFree's service is faster for a few reasons: They have a massive for-profit corporate parent company (iFastnet) with huge amounts of money and can afford millions in server costs, so servers aren't crowded. We're a tiny nonprofit with an operating budget of <$10k/year that owns our equipment and has no corporate parent. We can't easily afford more servers. Infinity Free is artificially crippled. Those restrictions tend to mean people don't stick around for very long, and they can't run larger applications if they do. Our free Johnny service and the one-time-donation Tommy plans aren't. To give you an idea, 96% of our shared hosting users are free users, or are one-time donors who donated as little as $1 for lifetime service.

Sure. Account reflux has been unsuspended. It may take a few minutes to work again. The other account can just be abandoned. It will delete itself in time since it's suspended. If you'd like to request it be deleted, please post from its matching forum account and we can do that.

The discord/dmarc/dkim/atproto ones have names, so you need to actually ask for, for example, _atproto.tenkyuu.dev to see it. The file you posted is only the domain itself (i.e. records with no name or with the name of the domain). The root domain shows the same thing as your file: https://dnschecker.org/all-dns-records-of-domain.php?query=tenkyuu.dev&rtype=ALL&dns=google For the named ones, they do appear if you specify their names. For example, the _atproto and _discord ones: https://dnschecker.org/all-dns-records-of-domain.php?query=_atproto.tenkyuu.dev&rtype=ALL&dns=google and https://dnschecker.org/all-dns-records-of-domain.php?query=_discord.tenkyuu.dev&rtype=ALL&dns=google This is the expected behavior for the records provided.

502 is related to Apache restarting and is normal. Should occur approximately every 2 hours and usually lasts 5-10 minutes. If you're unable to tolerate this, you would need to move to Morty, where the Apache restarts currently take under a minute. Note that on Morty, you'll get a 504 instead of a 502 during an Apache restart. 504 on Tommy can happen if your script takes too long. It basically means nginx timed out waiting for Apache to return content, which is usually caused by your website's code taking too long and not finishing. This can be caused by many things, including high server load or badly written code. 503 Service Unavailable is an unusual error to get on Tommy though, and I do see a few instances of that in your logs. I'm not sure what would cause this error specifically. Perhaps Krydos would know?

Account aloneguardspare has been deleted and you've been unsubscribed from emails. If you want the other account removed as well, please post here from the other account's matching forum account to confirm and we can do the same for that one too.

Looks good if I check the actual DNS queries. Our admin tools still show (cloudflare) next to your domain which is why I said that. There's probably a stale cache somewhere on our side, but that shouldn't impact the domain itself since public DNS is showing the right name servers...it's just a UI issue in our admin tools...

You're using Cloudflare so you have to do this yourself. That said, the webmail and www CNAMEs exist already on our servers (they're standard) as well as the MX. The TXTs for the email stuff are generated by a script when you request SPF/DKIM/DMARC if you request email support, no need to supply values as our system generates them automatically. I've gone ahead and done this for you. I especially did not use that DMARC record. You'd be hating yourself if I did...you'll be spammed to all hell by the automated reports (and probably end up suspended for disk space, the ruf can get you thousands of emails a day!), and your sent mail likely won't deliver on reject as most providers already have enough trouble accepting our mail without us telling them to throw it away... This is your zone file on our side. You'll need to use our name servers though for it to actually do anything: $TTL 14400 @ 86400 IN SOA ns1.heliohost.org. heliohost4.gmail.com. ( 2025041701 ; serial, todays date+todays 3600 ; refresh, seconds 1800 ; retry, seconds 1209600 ; expire, seconds 86400 ) ; minimum, seconds tenkyuu.dev. 86400 IN NS ns1.heliohost.org. tenkyuu.dev. 86400 IN NS ns2.heliohost.org. tenkyuu.dev. IN A 64.62.151.106 tenkyuu.dev. IN AAAA 2001:470:1:1ee::2009 ipv6 IN AAAA 2001:470:1:1ee::2009 tenkyuu.dev. IN MX 0 johnny.heliohost.org. mail IN CNAME tenkyuu.dev. www IN CNAME tenkyuu.dev. ftp IN CNAME tenkyuu.dev. webmail IN A 64.62.151.106 webmail IN AAAA 2001:470:1:1ee::2009 tenkyuu.dev. IN TXT "google-site-verification=gP9DbLrjLTsnPdCxCB4aFindIrtjQTovp2uVO5OX_Ec" _atproto.tenkyuu.dev. IN TXT "did=did:plc:q74gsah26xz3q4qoe5ixx5jx" tenkyuu.dev. 14400 IN TXT "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all" _dmarc 14400 IN TXT "v=DMARC1; p=quarantine" _domainkey.tenkyuu.dev. 14400 IN TXT "o=-" default._domainkey.tenkyuu.dev. 14400 IN TXT ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+SDLc/Hl5PNixlC3Z1QqVI5F0WQUTC0wA2GHBtcHm+cqyRxqCWP7OmmV5Z7Vn3nos10c8TB7chpdkPiTVeO53mrpK6ZC9fjhlfFajdLReXJvRhqR+MBCwUEw1IimwFUz35YIRwqJ2bHaqvtjhuH4oOZ45qq79GB9gsc5OGC/A74pvZBOzMt1zYo3BvwUNo2LT" "gcyMDTunY+ZU15PBFyE34tj8iniPctiznyx+MboWzR4FCG/igoSwuksUm591bW8PblllmtUzdIQi7ORn9P+JO+bCW29gJlJ77wxupzvelwUMbi/iNWrCnyVbJVNxHxGQTu4jzvMg74BfIGZ1YErmQIDAQAB;" )

The account igorhelio has been unsuspended, it may take a few minutes to work again.

We have nothing to do with gaming (though you could use our service to host a game website or server). Is there something we can help you with?

You're suspended for having more than one account. Users are only allowed to have one account. Which one would you like to keep? (It's worth noting that while your particular case did not receive any notice of the multiple account violation, we improved this process about 2 weeks after your suspension occurred. If it happened today, you would've gotten an email 24 hours before your suspension telling you that we suspect you're violating the TOS and asking you to explain).

There's a whole bunch of issues here...your curl command returns a 301 because you used HTTP instead of HTTPS. CURL does not follow 301 redirects by default. <html> <head><title>301 Moved Permanently</title></head> <body> <center><h1>301 Moved Permanently</h1></center> <hr><center>cloudflare</center> </body> </html> Using HTTPS, the certificate revocation check fails due to Cloudflare. Not sure how to fix this on linux. curl -H "TOKEN: My_Super_Secure_Token" https://tenkyuu.dev/cgi-bin/submodule_update.py curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate. I'm calling the script from my Windows box to debug it, and I just suppressed the error with --ssl-no-revoke, but that's reportedly not supported on linux. curl --ssl-no-revoke -H "TOKEN: My_Super_Secure_Token" https://tenkyuu.dev/cgi-bin/submodule_update.py Received token: My_Super_Secure_Token Starting submodule update... Error updating submodules: Command '['git', 'submodule', 'update', '--init', '--recursive']' returned non-zero exit status 1. I messed with the Python file a bit to try and get the stdout of git to show up, but had no luck. It just fails with code 1...

We don’t sell domains. You have to buy domains from a domain registrar like namecheap. Once you buy a domain, you just set the name servers on the domain to ns1.heliohost.org and ns2.heliohost.org then ask us to add it to your account.

I'll have to take a look when I'm on a computer, but I can see just from the screenshots you posted that the path in the os.chdir command is wrong. It should be /home/tenkyuu.dev/git... The path you have listed as missing the domain ( your home folder is /home/tenkyuu.dev)

Krydos has to upgrade VPSes manually. The VPS upgrade process is not automatic, and requests can take 24 hours or longer to be processed.

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.