New Topics

I've added laptoprecordsmanager.helioho.st to your account for you. Please note that it may take up to 2 hours for the domain change to take effect. 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 For the remote access part of your request, please can you confirm which database user name you want to have remote access? For remote access, our root admins need to know your hosting account username, database name, and the database user name you want to have access. - Hosting account username: dipeshshrestha - Database name: lrmdatabase - Database user name you want to have remote access: Please confirm? You can find the details required by the admins in our technical documentation Wiki here: https://wiki.helionet.org/PostgreSQL_Database_Remote_Connection_Error#How_to_Request_Remote_Access_to_PostgreSQL

DNS recreated.

The code itself isn't the cause of your load, it's systemd. Whenever a process is running under a user account (CGI execution, scheduled tasks, sftp, etc.), systemd causes load for that account. That load counts even though the script itself uses next to nothing. The load from systemd is basically directly correlated to the amount of time you have processes running. The more stuff you run (or leave running), the higher it gets. You can even get suspended for load by connecting to sftp and leaving the open connection idle. Looking at what's running, the Python apps and the PHP called via scheduled tasks are likely what's causing systemd to be running for your account. Your load by process: 14.71 GB 0 (sd-pam) 12.37 GB 5.45 k /usr/lib/systemd/systemd --user 6.99 GB 34.7 /opt/plesk/php/5.6/bin/php -f httpdocs/airspace_around_me/web/api/ogn_bridge_control.php 5.46 GB 212 python3 -u ogn_bridge.py 4.73 GB 26 /opt/plesk/php/5.6/bin/php -f httpdocs/airspace_around_me/web/api/collector_control.php 3.07 GB 137.4 python3 -u collector_hosted.py 1.37 GB 41.5 /opt/plesk/php/8.3/bin/php-cgi -c /home/system/ogn.helioho.st/etc/php.ini 45.33 MB 0.4 /opt/plesk/php/8.5/bin/php -f httpdocs/airspace_around_me/web/api/notam_control.php 45.20 MB 0.2 /opt/plesk/php/8.4/bin/php -f httpdocs/ogn_tools/scheduled_daily_postprocessing.php 41.24 MB 2.1 python3 -u notam_collector.py 18.11 MB 0.3 python3 Scripts/puretrack_labelsConverter_json_to_db.py

Closing since this was being handled over in email support which is now working again. https://helionet.org/index/topic/67209-hh546672-is-there-an-alternate-way-to-pay-mortys-19-fee/

root@control [~]# dig +short A @ns1.heliohost.org affittimastrogiuseppe.helioho.st 64.62.151.106 root@control [~]# dig +short A @ns2.heliohost.org affittimastrogiuseppe.helioho.st 64.62.151.106 root@control [~]# dig +short AAAA @ns1.heliohost.org affittimastrogiuseppe.helioho.st 2001:470:1:1ee::2009 root@control [~]# dig +short AAAA @ns2.heliohost.org affittimastrogiuseppe.helioho.st 2001:470:1:1ee::2009 Should be good to go now.

All of your German logins are from VPNs. You probably just forgot to connect to your German VPN one time, and revealed your country. Obviously our US government is very anti-Iran right now, so it's not worth getting shut down and 7000 other users losing their hosting because we knowingly allowed one Iranian to use our hosting. Our backup system is broken right now, but we should be able to get it working again in the next few days. I'll reply to this email once your backup is available for download.

Thank you so much for the rapid assistance.

Missing DNS zone fixed. It may take a few minutes to be available everywhere.

Missing DNS zone fixed. It may take a few minutes before its available everywhere.

DNS for zone thedannified.helioho.st is not missing. We are currently unable to delete domains due to the recent DNS server failure. Work on restoring that functionality is ongoing.

Fixed missing DNS zone. It may take a few minutes to resolve and up to 4 hours for everyone to see it.

Fixed DNS zone. It may take a few minutes to start resolving, and up to 4 hours for everyone to be able to reach it.

You re suspended for excessive cpu load caused by overuse of scheduled tasks. I have disabled all scheduled tasks that run more frequently that once a day and unsuspended you. Please reduce the frequency on your scheduled tasks. Unsuspended. It can take up to two hours for your domains to function...

DNS recreated.

DNS recreated.

We don't really rename domains, we add the new one and remove the old one. I've now added ursafe.heliohost.us to your account. Please give it up to 2 hours to start working. Because of the maintenance and repairs that are ongoing, we cannot yet remove domains. Once we can remove them, either myself or another member of staff will remove the butangfindr one from your account and update this thread to let you know.

DNS recreated.

Missing DNS zone fixed. It may take a little while before the changes propagate.

First of all, sorry for the long downtime on our main website. Over the past few years our main database has just been getting slower and slower. It was last rebuilt in 2017 so it was well overdue for an upgrade. A few days ago the main database was so slow that we decided to take it offline, and rebuild it with a modern operating system and up-to-date software. We expected the downtime to last a few hours, but then during the upgrade everything fell apart. While Cody was down, his twin brother Brody got so sad he died too. This happens sometimes with twins because they can't live without each other, which is cute but also very tragic. So then, with both a dead Cody and a dead Brody, we had no nameservers, no main database, no website, no forum, no wiki, etc etc etc. But here at HelioHost we never give up. No matter how many servers explode, or how many evil for-profit corporations try to destroy us we will never give up. It took a few days, but our main website is back online, both of our nameservers are back online, our forum is working again, and a lot of the stuff going on behind the scenes are working again too. That said, there is still plenty of stuff that isn't working yet. The main issue seems to be that during the upgrade of the nameservers a lot of DNS zones got lost, so some websites are offline. If your domain gives a DNS error when you try to visit it in a browser let us know and we can take a look. It usually only takes a few seconds to recreate the DNS for you. We're still working on getting everything functional again, but we're making progress. Thanks for everyone's patience during this crazy rebuild.

Thank You!! Working again!

You spelled this one wrong. It's actually ai2ai.homes. This one is wrong too, as it hasn't even been purchased. https://www.namecheap.com/domains/registration/results/?domain=davosparsenn.homes You do have a domain named davosparsenn.com which is working fine. DNS recreated.

DNS recreated.

Domains added.

Thanks a lot. I can login now, but page does not load. I think I have to wait a bit...

Thanks, it's working. Sorry for troubles.