Jump to content

Krydos

Chief Executive Officer
  • Posts

    25,558
  • Joined

  • Last visited

  • Days Won

    915

Posts posted by Krydos

  1. It looks like 28 accounts had their data corrupted from the power outage, and yours was included. I have restored your account from the most recent backup we had for you. Keep in mind we don't regularly back up accounts for people, and we always encourage people to make frequent backups of their own data. Now that your account works again you should be able restore any newer backup that you made yourself.

  2. HelioHost is happy to announce that we now support PHP 8.5 on the Morty plan. The Tommy plan will be upgraded to have PHP 8.5 soon, and after that Johnny will have it installed too.

    • Like 1
  3. WSGI control access has been enabled on the domain casamarcial.com.br. To restart your Flask app and load new code changes in simply edit /home/talesaz.heliohost.us/casamarcial.com.br/michi/flask.wsgi. Adding a blank line, removing a blank line, adding a space, or removing a space are examples of editing the file. As long as the last modified timestamp changes it will clear the server cache. Let us know if you run into any issues.

    • Thanks 1
  4. No problem. Let us know if you need help with anything else. We used to only allow 2 cron runs per day, and you're running about 1200 per day so I don't consider this an issue that your load is right around 8k per day. 1200 cron runs per day is pretty generous for a free service.

  5. This morning the city in California where our datacenter is located had a power outage. It took the city a few hours to restore the power, but once the power was back on all of our servers booted up. Everything should be online and fully functional now, but if you notice any issues please let us know.

  6. In November you asked us to allow PostgreSQL connections to pg-service-dm-khanin-project.d.aivencloud.com on port 23579. Unfortunately our firewall doesn't allow us to whitelist domains. We can only whitelist numerical IP addresses. In November the domain pg-service-dm-khanin-project.d.aivencloud.com resolved to the IP 85.9.195.148. Today that same domain resolves to the IP 85.9.193.5. If the IP continues to change every month I recommend you contact this aivencloud and ask them if they can put you on a static IP. Is it working again now?

  7. We had another person report a similar problem. They actually answered our questions though. They said they were using Google Chrome, and when they disabled their plugins the signup process started working for them. They said the plugins they disabled were Scribe and Meta Pixel helper. I have tested signups with both of those plugins installed, and still can't reproduce the issue. Not sure what is going on, but if you're still having issues let us know and we can investigate further.

  8. 41 minutes ago, mimmobile146 said:

    now i'm facing 503 error on my new files , kindly advice!

    503 errors are normal for up to 2 hours after being unsuspended. It's been about 2 hours now since you were unsuspended for the second time so they should have resolved themselves now. If you're still seeing 503 errors let us know.

    44 minutes ago, mimmobile146 said:

    no , since my first suspension i never logged into my account

    If you get suspended for a third time don't ask for an unsuspension unless you are ready to fix the issue immediately.

  9. 28 minutes ago, mimmobile146 said:

    this is my only first suspension i have not been suspended before

    Your first suspension was at 2025-12-20 13:17:12 for exceeding the 200 GB per day memory limit. You asked for an unsuspension, and were told to fix the issue immediately. Your first suspension ended at 2025-12-20 21:01:11 and then about 3 hours later you had not fixed the issue, or had made the issue worse somehow, and your second suspension started at 2025-12-20 23:59:48 because 76 simultaneous copies of your Telegram bot were running.

  10. Let us know if you find a vulnerability for a particular kernel, and we can update the server. Generally we keep the server fairly up to date anyways so it's unlikely that anything like that will be an issue. It seems like you must be new to Linux because it's literally always been this way. We used cPanel from 2005 until 2021 and it was the same way too, and now Plesk is the same from 2021 to 2025. If it was a security issue I think cPanel or Plesk or CentOS or Alma Linux would have fixed it in the last 20 years.

  11. MoneyBroz tried to do a backup for you last night, and was having trouble with it so I told him to give up and I'd take a look at it today. I took a look at it myself just now, and I'm unable to access the filesystem either. It looks like it locked up too many times, and was forcibly rebooted too many times and it destroyed the filesystem. I went ahead and started the rebuild for you. You'll get an email in a few minutes when it's done.

    • Like 1
×
×
  • Create New...