Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/31/2021 in all areas

  1. Tomorrow, 2021-08-30 starting around 7pm UTC, we will be doing maintenance at our data center which will cause downtime on all of our servers and VPS, including our main website heliohost.org and our forums helionet.org. We estimate the downtime will probably be around an hour for each server as long as we don't run into any significant issues. Our last fundraiser was successful and we are now installing the hardware that we raised the money to purchase. This will increase the performance of Johnny, Ricky, and all of our VPS as well. The fundraiser also paid for network hardware speed improvements which were completed earlier which allows for faster downloads from all of our servers and mitigates the effects of ddos attacks. We will also be installing some hard drives for a new server named Morty that we hope to release in a few months after we finish rebuilding Tommy, Ricky, and Johnny with Plesk.
    2 points
  2. @yoreparo - this is done. Please check your email for the details.
    2 points
  3. Is it the VPS that is down, or just your website? If you can ping the VPS, than the reason is probably that the webserver did not automatically restart. I had this problem, too, several servers not being running after the VPS had been shut down. Just check the servers and restart them...
    1 point
  4. Awesome! Looking forward to Plesk and Morty too (well I'm not going to use them since I have a VPS, but still feels good to know it's there 😁). My VPS had become pretty slow during March/April but now it's back to normal, so I guess this reinforces that stable feeling. My team has been hosting our main website on Netlify till now, and we're planning to switch to a full-fledged Ghost on a HelioHost VPS, so the timing couldn't have been better 🙃 Re the reboot: nginx and some other services failed to start for some reason, so I had to SSH in manually and start them. In case anyone else ran into problems, the solution is to run `systemctl status service` and then `systemctl restart service` where service is the service name, such an nginx (web server), mysql (database), postfix (email sender), dovecot (email receiver), etc. Of course Hestia might handle all this by itself; I'm not sure (I use YunoHost) 🙂
    1 point
×
×
  • Create New...