Jump to content

This stream auto-updates

  1. Past hour
  2. Last week we had an issue with Brody and Cody, our nameservers, and we have been very busy during the subsequent days rebuilding them and getting everything back online. Since the older brothers were getting so much attention, the youngest brother, Johnny, threw a tantrum and demanded all of our attention. We noticed Johnny was acting up a couple hours ago, and shut him down to take a closer look. It turns out the master boot record needed to be rebuilt and the partition data needed to be reconstructed as well. We have access to the hard drive now, and it seems like most of the data is still intact. This could indicate that the hard drive is going bad though, so we've already started making backups of everything. It's actually interesting timing because Johnny was already scheduled to be rebuilt in the next month or two anyways, so we've just accelerated that plan. While the backups are being created we will be building a new Johnny on newer hardware and a more reliable hard drive raid array. Once all of the backups are ready we will let you know, so you can download them. If you'd like to get your website back online immediately, the Morty and Tommy servers are still operating normally, or you could even move to a VPS as well. If you'd like to stay on Johnny we will get the new server finished and the backups restored as soon as possible, but there is no promised ETA and it may take a week or maybe even longer.
  3. Today
  4. Johnny was down for a bit, and I don't see you in the blacklist. Are you still unable to access it? As for uptime, if you need something with proper uptime, you need a Tommy or Morty account. Johnny is meant to be an unstable test server, so this sort of thing is basically normal for it. Tommy and Morty have much better uptime. (Also, it's normal for the login page to not work when your account's server is down.)
  5. Thank you. Restoring a previous backup fixed the problem. The problem happened when I deleted the entire /jpnew/ folder from the server and uploaded another one from the PC. I already had a backup, which I restored, and everything is OK. For some reason, local folders can't work, as they result in non-adjustable persmissions problem (persists even if fixed). I should deal with internal contents, instead of deleting the enitre folder and uploading another. Thanks again.
  6. Hello, Google Workspace email for ajira.org.uk is failing SPF and DKIM authentication. Could you please add the following SPF TXT record to the domain DNS: Type: TXT Host: @ Value: v=spf1 include:_spf.google.com ~all I also need assistance adding/enabling DKIM for Google Workspace if DNS is managed on your side. Thank you.
  7. Copying Krydos's response since you also emailed us about this...
  8. DNS recreated.
  9. DNS recreated, and MX records set.
  10. There is no module named MySQLdb, so I installed mysql-connector. If that's not the module you need please attempt to be more specific. You can see the list of installed modules for Morty2's Python 3.14 at https://morty2-info.heliohost.org/pyinfo/info3.14.py
  11. Username: sameerswedev Server: Johnny Main Domain: sameerswedev.heliohost.us Request: > I would like to change my main domain to a shorter name. I have backed up my files and understand that this change may break existing configurations. Preferred Names (in order of preference): api.heliohost.us xapi.heliohost.us apix.heliohost.us apis.heliohost.us dev-api.heliohost.us devx.heliohost.us nixp.heliohost.us api-bin.heliohost.us dev.heliohost.us sysq.heliohost.us (Note: If all are taken, please use s-api.heliohost.us) Additional Subdomains: Once the main domain is changed, please add the following subdomains: py.[chosen-name].heliohost.us (Root: /py-dev) node.[chosen-name].heliohost.us (Root: /node-dev) I am aware of the 5-domain limit on the Johnny server and this request keeps me within that limit. THANK YOU very much for your time and help!
  12. Missing DNS zone fixed. It may take a little while before its available everywhere.
  13. Domain added, it'll take effect in about 90 minutes.
  14. Yesterday
  15. I've added those domains 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 they don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache
  16. Those domains have been added for you. Please note, they 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
  17. Sure. Your VPS has been powered back on, and I put a note on your account that you'll get a new payment set up before 2026-05-21. It was already emailed to you, but here is the payment link again that you can use as soon as you receive your new card: https://heliohost.org/vps/pay/?code=0mUdTg6zUSJFE5QM
  18. Thanks. I had the issue before and implemented something to kill itself when the last instance is still running so there should only be one. apparently this doesn't work anymore.
  19. Works just fine now. Many thanks!!
  20. Thank you for the reply. I will inform about the domain the moment it transfers to Spaceship from my old hosting company. Max time 5 days, it says.
  21. Your account has been reset, and you'll receive an email shortly with a link to complete the process and create a new account. If you need any data from your old account, a backup of your old account may be available at https://heliohost.org/backup/ once the process is complete. Note that if your account was reset due to malware or a Terms of Service violation, a backup of your account will not be created.
  22. The second name server was still missing the zone. Should be fixed now. Note that between monday and now, your site was in fact available for many users, it just depended on which name server their system decided to query. If it picked ns1, it worked, if it picked ns2 it did not.
  23. Okay, thanks for the answer.
  24. DNS recreated.
  25. 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. 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
  26. Try downloading your backup from https://heliohost.org/backup It should be working now. Yes, you're welcome to use our hosting again in the future as long as you aren't from a country that the US has active sanctions against.
  1. Load more activity
×
×
  • Create New...