Krydos

You filled your 50 GB entirely so that's why nothing is working anymore. /dev/mapper/ubuntu--vg-ubuntu--lv 46G 44G 0 100% /

Why not reuse a database that already has remote access enabled? Why do you need 8 different databases?

DKIM, SPF, and DMARC have been set up for the domain marckeeley.helioho.st. We recommend sending a test email to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.

WSGI control access has been enabled on the domain man95.heliohost.us. To restart your Flask app and load new code changes in simply edit /home/man95.heliohost.us/public_html/flasktest/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.

You already have remote access for 7 databases. Do you really still need access to all of these? Also I'm considering adding a limit to the number of remote PostgreSQL access requests because of you. We used to allow unlimited domains, until someone abused our generosity. We used to allow unlimited database connections, until someone abused our generosity. We still allow unlimited PostgreSQL remote access requests, but you may be the person to change that policy.

It works for me. If you're still seeing the default page don't forget to clear your browser cache. Since you're using Wordpress keep a close eye on https://heliohost.org/dashboard/load/ because Wordpress is really bloated software and it causes a lot of load, even with very little traffic. We have a whole Wiki article explaining how bad Wordpress is in case you want to come up with alternatives or ways to reduce your load https://wiki.helionet.org/misc/wordpress

Yeah, you're right. You are using a lot of CPU too. You have 8 CPUs and 4 GB memory now. Let us know if it's faster.

I did notice a little swap usage. If the load is spiking during backend operations it could indicate that the server is still running out of memory. We could try bumping you to 4 GB to see if those backend tasks run smoother.

Microsoft uses the Benevity service to dispense donations to non-profits, and we've received donations from Benevity before so we assume it will work to donate Microsoft points. Two people have donated 1000 points recently with the hopes of getting moved to Tommy, but as of today we still haven't been able to verify the donations. I suspect Benevity only deposits money to us once a month, and even then we're not sure we can determine who donated what.

An invite has been sent. Please let us know the username that you choose for the new account once it is created so an exception can be made in the multiple account detection system so you don't get suspended for logging in to two accounts.

Also, is there any particular reason you're using PHP 7.4? Wordpress runs best on the latest stable version of PHP which is 8.3 and it's already installed on your VPS. If you're running an old version of Wordpress that requires PHP 7.4 I recommend updating to the latest version of Wordpress and switching PHP to 8.3.

You may need to create a free GTmetrix account to see the full report.

Take a look at this report https://gtmetrix.com/reports/gzmoperformance.co.uk/4HYl6XH6/#structure The main issues it lists is excessive dom size for the total blocking time TBT, and explicit image sizes for the cumulative layout shift CLS. They also have a guide specific to Wordpress that may be useful https://gtmetrix.com/wordpress-optimization-guide.html

I changed some of your timeouts to longer values. Let me know if you get another timeout error.

That's what caused it then. Your account and your son's account has been unsuspended. An exception has been added to the multiple account detection system so you shouldn't get suspended again.

Does the page actually sit there loading in the browser for 500 seconds before it gives that error? Perhaps there are multiple timeouts in play. Nginx, Apache, and PHP all have timeouts that could be causing this. If the error happens after 30 or 60 seconds it clearly isn't hitting the 500 timeout.

Your VPS actually looks decent right now. 0.12 load, and 1.5 GB free memory.

It looks like your Cloudflare AAAA record is wrong. If you try to access the site via IPv4 it works, but if you try IPv6 it shows the alien. The correct AAAA record for your VPS should be 2001:470:1:1ee::109

Your VPS has been rebuilt with Ubuntu 24.

Try increasing the Apache and PHP timeout. Here is a guide I found that may help https://fornex.com/en/help/php-ini-hestia-cp/ Since you have such a large database it takes longer than 120 seconds to optimize it all. Maybe try 300 seconds, and if it still times out you can raise it even more.

DKIM, rDNS, SPF, and DMARC have been set up for the domain jchang.heliohost.org. We recommend sending a test email to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.

What does the error log say when you get the gateway timeout?

I bumped you up to 3 GB memory, and I was noticing some CPU bottlenecking earlier too so I increased your CPUs from 2 to 4. Let us know if it is performing any better now.

Installed. You can see the current list of installed modules and their versions for Johnny's Python 3.12 with this link https://krydos2.heliohost.org/pyinfo/info3.12.py

15 minutes after the reboot you website is loading a little faster, but you are already down to 90 free MB of memory, 400 MB of swap used, and your load is around 2.00. I'm going to increase you to 2 GB memory.