New Topics

Solved topic thanks

I've been trying to extract a zip folder into one of my domains; ngo.helioho.st, but it delays and doesn't finish extracting or ends up showing errors. The folder name is 'node_module-linux.zip' and it's size is 185MB. On my local, the extracted size is 570MB. I still have ample space on my alloted space so i don't get why i can't extract it succesfully. Infact, other extractions have earlier failed for other domains before i cleared them out.

server: johnny username thofficial

That suspended screen is not ours, so we cannot assist with that. You'll need to contact the developer of whatever game or program that is to get assistance.

Hello, Thank you for the reply. I already tried enabling remote access in Plesk, but the issue is: The “Allow remote connections from” setting does NOT save. Whenever I enter % and click Save, it automatically resets back to “Allow remote connections from any host.” Because of this bug, remote MySQL access is not actually enabled, and my backend on Railway still receives connection errors. Could you please manually whitelist % for my database user? Database: lostandfound_db User: lostandfound_user Server: Johnny Host to allow: % (all hosts) Thank you

See:

Domain added, it'll take effect in about twenty minutes.

Thanks for your quick response!

Glad you're on board with us! the subdomains have been added to your account. it can take up to 2 hours for them to start working.

I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

It looks like PayPal attempted to bill you on 2025-11-25 and failed. PayPal will automatically try billing you again on 2025-11-30. There is no way for us to force PayPal to attempt to bill again before then. If the payment fails again on 2025-11-30 we will email you.

I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

i visited johnny.heliohost.org too

Set. # dig +noall +answer -x 64.71.156.101 101.156.71.64.in-addr.arpa. 21539 IN CNAME 101.subnet96.156.71.64.in-addr.arpa. 101.subnet96.156.71.64.in-addr.arpa. 14339 IN PTR fatehsystems.com. # dig +noall +answer -x 2001:470:1:1ee::21 1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.e.e.1.0.1.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 14400 IN PTR fatehsystems.com.

Looks like this was resolved over email:

Done thank you so much for your co-operation's Really mean a lot

We haven't supported Java since 2021. We're hoping to bring this functionality back in the future, but there's currently no timeframe for when this will be offered again. In the meantime, you would need to purchase a VPS and install tomcat on it to run this.

Your account is being reset. When the process finishes, you'll receive an email with a link to create a fresh account. If you need any data from your old account, a backup will be available at https://heliohost.org/backup/ once the reset is complete.

Great, thank you so much!

Your website looks fine to me. A root administrator was conducting some server maintenance earlier, so you may have seen that error as a result, but it's fine now. If you're still seeing the SNI error, clear your browser cache.

In that case we recommend adding the new domain as an addon domain (not an alias) and then you can use .htaccess to redirect all the traffic from journalpulse.heliohost.us to synapsejournals.dedyn.io. I set the new domain as your main domain, and the heliohost.us subdomain as an addon. I also put an .htaccess file on the journalpulse.heliohost.us with these contents: RewriteEngine on RewriteCond %{HTTP_HOST} ^journalpulse.heliohost.us [NC,OR] RewriteCond %{HTTP_HOST} ^www.journalpulse.heliohost.us [NC] RewriteRule ^(.*)$ https://synapsejournals.dedyn.io/$1 [R=301,L,NC] This should redirect everything to the new domain with a permanent redirect which means search engines and browsers should update their links. This .htaccess should preserve the path and filename so if someone goes to journalpulse.heliohost.us/path1/file2 it should send them to synapsejournals.dedyn.io/path1/file2, but if you're having any issues feel free to customize the .htaccess as you need. Eventually if you stop seeing any traffic to the heliohost.us subdomain in your web statistics let us know and we can remove the domain entirely to save server resources. Let us know if you need help with anything else.

Duplicate request: https://helionet.org/index/topic/66310-alias-domain-request-synapsejournalsdedynio/?do=getNewComment

Correct, it's our servers (specifically, the lack of integration between Plesk and our DNS) that don't support it.

Thanks, it works now.

Probably because SPF and DKIM aren't set up (you have to request that, it's not enabled by default)...most mail providers will just throw your email away unless those are configured. DKIM, SPF, and DMARC have been set up for the domain qiyemailset.helioho.st. We recommend 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. Try the test above, then try sending your normal emails again