New Topics

I mistakenly used the website’s ‘password-protected directories’ feature to secure the root directory, and now my entire website is inaccessible. The error log reads: “[Sat Mar 14 13:49:44.614786 2026] [authn_file:error] [pid 872695:tid 872727] (2)No such file or directory: [client 13.250.42.105:0] AH01620: Could not open password file: /home/system/a1642979808.helioho.st/pd/d..httpdocs, referer: https://a1642979808.helioho.st/ [Sat Mar 14 13:49:44.812037 2026] [authn_file:error] [pid 872695:tid 872721] (2)No such file or directory: [client 13.250.42.105:0] AH01620: Could not open password file: /home/system/a1642979808.helioho.st/pd/d..httpdocs, referer: https://tommy.heliohost.org/ [Sat Mar 14 13:49:45.170750 2026] [authn_file:error] [pid 872695:tid 872719] (2)No such file or directory: [client 13.250.42.105:0] AH01620: Could not open password file: /home/system/a1642979808.helioho.st/pd/d..httpdocs, referer: https://tommy.heliohost.org/ [Sat Mar 14 13:49:45.646896 2026] [authn_file:error] [pid 872695:tid 872730] (2)No such file or directory: [client 13.250.42.105:0] AH01620: Could not open password file: /home/system/a1642979808.helioho.st/pd/d..httpdocs, referer: https://a1642979808.helioho.st/ [Sat Mar 14 13:49:54.095130 2026] [authn_file:error] [pid 872417:tid 872460] (2)No such file or directory: [client 13.250.42.105:0] AH01620: Could not open password file: /home/system/a1642979808.helioho.st/pd/d..httpdocs [Sat Mar 14 13:49:54.736687 2026] [authn_file:error] [pid 872695:tid 872742] (2)No such file or directory: [client 13.250.42.105:0] AH01620: Could not open password file: /home/system/a1642979808.helioho.st/pd/d..httpdocs [Sat Mar 14 13:49:55.117294 2026] [authn_file:error] [pid 872695:tid 872737] (2)No such file or directory: [client 13.250.42.105:0] AH01620: Could not open password file: /home/system/a1642979808.helioho.st/pd/d..httpdocs, referer: https://a1642979808.helioho.st/flasktest/ [Sat Mar 14 13:50:22.030473 2026] [auth_basic:error] [pid 872695:tid 872718] [client 13.250.42.105:0] AH01618: user 1642979808@qq.com not found: /flasktest/”How should I recover

To whom it may concern; Since the recent changes I ordered for my account, I have been experiencing an SSL issue whenever I access the https://news.burken.com on my account. I fist get the "Your connection to this site is not secure" warning in Chrome then it resolves to the Morty cPanel login page, Can't figure out what's causing this issue. Any help with this would be appreciated. Chris

WSGI Control Access is only available on the Morty server, or a VPS. You can read more information about it here: https://wiki.helionet.org/Flask#Request_WSGI_Control_Access

I might as well do this then. do you have the direct url to go do the upgrade or is it easily located in the heliohost account info. going to look for it. Thanks for the prompt support...

The PHP max_input_vars on your domain as been changed to 3500.

Hello! 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

Dear @wolstech and @Krydos, thank you so much. All seems to be working fine now. 🙂 Kind regards. ))

Thanks. You guys are awesome!

Thank you!

We are not a domain registrar and cannot accept domain transfers. That said, you can host your domain here by changing your DNS records (use NS records pointed at ns1.heliohost.org and ns2.heliohost.org, or A and AAAA records that can be seen in Plesk) and requesting the domain be added to your account.

Domains added, the changes will take effect in about 40 minutes. You'll need to create an A/AAAA record to Morty's IP or switch to HelioHost's nameservers for the domains to work.

Refund issued, and account deleted. Thank you for complying with our terms of service.

Added.

Your account is being reset, you should receive an email to recreate your account shortly.

SSH is not available on shared hosting accounts due to security reasons, if ssh is needed than you will need to get a VPS.

Closing due to inactivity since there has been no response in this thread for over a week. If you're still having this issue or need help with something else please open a new ticket.

I'll see

That domain cannot be added because the contents of your account violate the terms of service. Note that this prohibition also includes selling access to IPTV and related services, even if the actual content is hosted elsewhere, becuase IPTV and related services are illegal in the USA where we are located (copyright infringement).

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've added those 2 domains to your account for you. Please note that it may take up to 2 hours for the domain changes to take effect. For the .lat domain, you must set up your DNS with your domain registrar for the domain to work. To do this, 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 the domains don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

3.9.23

Alright, I have deleted the new VPS132 that you created, transferred the new subscription to the old VPS35, and you should be good to go. If this happens again in the future please note that you can just click the link in the email to pay for your existing VPS rather than creating a new VPS. Less work for you, and less work for us too. Thanks for being a VPS customer.

This seems resolved. I just modified the dispatch.wsgi and *.htaccess; the pings and logs returned to normal. I will check back again later today.

Removed.

Readded Digital Plat. URL linked is a referral for an extra domain slot. They recently fixed a lot of bugs and updated their website and dashboard. Will add working links later when I create the websites.