Jump to content

This stream auto-updates

  1. Past hour
  2. Hello! As you've been advised on 14/06/2026 08:59, we cannot accept your attempts to set an ETA/SLA. For support response timelines (SLAs and ETAs), check: https://wiki.helionet.org/ETA All staff are unpaid volunteers who donate their free time outside of real-life commitments (paid job, school, family, etc.) so trying to say things like "Priority: 9/10, Urgency: 10/10" will not have an impact on the free time we have available to donate to Heliohost users. In fact, trying impose a deadline on unpaid volunteer staff can give a negative impression. Not all unpaid volunteer staff will work faster when someone tries to insist that they do. Not all unpaid volunteers will be pushed into hurrying because someone impatient says they should. All unpaid volunteer staff are free to choose who they assist, and not all of them will be pushed into hurrying if one user decides to claim they are more important than everyone else who needs help by trying to add a "9/10" in a request for help. Most for-profit hosting companies have a staff of full time employees who sit around providing support and working 40 hours a week. It's very rare for any of our volunteers to work more than an hour or so each day. None of our volunteers are required to log a certain number of hours and may come and go as they please. We run this organization in our free time, and if we don't have very much free time things don't get done very quickly. If we aren't having fun volunteering, providing support, chatting with the community, and developing new features then we take a break and do things that are more fun for us. This is why we don't have SLAs or ETAs for new features or repairs, and this is why things move a little slower than a for-profit company that you might be used to dealing with. Since all HelioHost staff are unpaid volunteers, so there is no guaranteed timeframe for a response to support requests. Our best efforts to respond within 24 hours can be impacted by several factors, including but not limited to: - Time zone differences (most staff are based in North America) - Work - School - Family - Other real-life commitments As I shared with you on 14/06/2026 08:59: We try to action all support requests within 24 hours however this is not a guaranteed timeframe. Thanks!
  3. Updated and unsuspended. Your account may take up to 2 hours to function.
  4. Today
  5. The files from your old account can be downloaded from https://heliohost.org/backup/
  6. Hi Wolstech, Following up on this thread; wanted to flag something I found while cleaning up after the recent incident, in case it's useful for your records. While reviewing my ngo.helioho.st site (a separate, non-WordPress domain on this account) I found two files that don't belong there: a heavily obfuscated backdoor named mac.php (last modified June 11, ~7:49 PM), and an injected index.php containing a remote-eval payload pulling from 63.141.235.34, plus a redirect to a suspicious shortened link, swiy.co/goodrich555 (modified June 13, ~7:07–7:12 AM). Both timestamps are before your review where you mentioned nothing looked suspicious outside lda.ng, so this looks like it's from the same intrusion window, just on a domain that isn't WordPress and may not have been part of that check. Tried backuing up existing WP installs like ths.helioho, but i encounter Host Build interrupts sue to things like allowed runtime and PHP max execution. I've already renamed both files to .infected to disable them and remove them from execution and I'm restoring a clean copy of that site myself. I'm not asking for another account-wide reset; this is contained and I'm handling it, but since I don't have shell access to search file contents across the rest of the account, Since this looks like leftover from the same incident rather than a new one, I wanted to flag it rather than sit on it. Would it be possible to do a targeted check for similar files on my other domains rather than a full account reset?-since the rest of the account otherwise appears unaffected. Happy to send over the exact file contents if that helps your scan. Thanks again for the help.
  7. I also wanted to let you know that when I go to the wiki, it says my ip is blocked or something. My ip address is 73.144.3.243 not sure what's going on with that, I can access everything else just fine.
  8. Yesterday
  9. Your current balance is $6.6407 plus $15 plus $3 bonus brings your new total to $24.6407. Based on your load for the last 30 days your new estimated expiration date is 2026-08-24. If your load increases this could run out sooner or if your load decreases it could last longer though. We'll email you occasionally to let you know how your balance is being used. Thanks for increasing your Morty balance.
  10. Number 2 is correct, you'll get a blank OS with SSH access to setup whatever you want. If you aren't used to the command line of linux then we can install a control panel such as Hestia for you.
  11. In order to reset your account we must first verify your email address. This is to prevent someone from pretending to be you to delete your data. The easiest way to verify your email address is to send an email with the text "please reset my account" to support@heliohost.org from the email address listed in the top right corner of https://heliohost.org/dashboard/ Once we've verified your email address we will be happy to start the reset for you.
  12. Are you able to access the wiki now?
  13. Installed. You can see the current list of installed modules for Johnny's Python 3.14 at https://johnny-info.heliohost.org/pyinfo/info3.14.py Installed.
  14. Alright, it looks like the Ubuntu 26 installer works again. You should have just received an email that your VPS is ready to go. Thanks for your patience and thanks for helping us test the new OS.
  15. Thank you, I am forwarding him how to archive the account.
  16. Yes, all good now. Thanks. On Sun, Jun 14, 2026 at 7:10?PM HelioHost Support wrote: > The issue was a DDoS on our wiki this morning broke a firewall rule that > is required to login. It should be fixed now. > > You may view the status of your ticket by visiting: > > https://helionet.org/index/index.php?showtopic=68298 > > Thank you, > HelioHost support > https://heliohost.org/ > https://helionet.org/ > >
  17. Last week
  18. Installed. You can see the current list of installed modules and their versions for Morty's Perl at https://morty2-info.heliohost.org/modules.pl
  19. The issue was a DDoS on our wiki this morning broke a firewall rule that is required to login. It should be fixed now.
  20. The issue was a DDoS on our wiki this morning broke a firewall rule that is required for the login system to work. It should be fixed now.
  21. We can reset your account for you. In order to reset your account we need to verify your email address. This is to make sure someone isn't pretending to be you to delete your data. The easiest way to verify your email is to send your reset request from the same email address listed in the top right corner of https://heliohost.org/dashboard/ while logged in.
  22. Hey Krydos, didn't consider that, I'll give it a shot with WinSCP and see if it'll accept the files. Thanks for the suggestion!
  23. Remote access enabled. host=65.19.154.90 port=5432 user=russwell_app dbname=russwell_reddit password=<set in Plesk>
  24. Is it possible to change the port that gateway01.us-east-1.prod.aws.tidbcloud.com is listening on?
  25. thank you !!!!
  26. 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.
  27. 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.
  28. 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.
  1. Load more activity
×
×
  • Create New...