Krydos

That rule only applies to Plesk accounts on Johnny or Tommy. VPS are allowed to send unlimited emails by default unless we start receiving spam reports for them.

That isn't your VPS IP address. It's a Cloudflare IP and they don't proxy port 465 for your mail. You need to connect to your VPS directly for mail.

What do you see when you go to http://portquiz.net:1373/ in a browser?

Here's what your Filezilla settings should look like. Here's what sftp command should look like root@control [~]# sftp -oPort=1373 an4s911@tommy2.heliohost.org The authenticity of host '[tommy2.heliohost.org]:1373 ([2001:470:1:1ee::2002]:1373)' can't be established. ED25519 key fingerprint is SHA256:XYCOOviohYA+fYhxWGH8qb+XrhhXnhaEKbP0J4CdGEw. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '[tommy2.heliohost.org]:1373' (ED25519) to the list of known hosts. an4s911@tommy2.heliohost.org's password: One common mistake that Wolstech didn't already mention is your username is all lowercase so if you try something like username An4s911 it will block you for trying to bruteforce our server.

DKIM, SPF, and DMARC have been set up for the domain greenroyaal.heliohost.us. 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.

Since the Wordpress install is specifically meant to be a store to sell 20k items, I'm pretty sure disabling WooCommerce plugins would disable the entire point of the site. I think the 100% full hard drive is more of a concern right now.

That's fine. I just needed to make sure you had a good reason for all this, and weren't just screwing around with us or something. Remote access enabled. host=65.19.154.94 port=5432 username=fudobi_admin_suteki dbname=fudobi_suteki password=<set in Plesk>

There is 23 GB in cache and 8 GB in uploads. Is that what you would expect? 12K ./boost-cache 16K ./webtoffee_iew_log 4.0K ./upgrade 23G ./cache 12K ./wpo-cache 16K ./webtoffee_export 20K ./webtoffee_import 331M ./plugins 208K ./wp-rocket-config 13M ./themes 9.7M ./languages 8.0G ./uploads 56K ./mu-plugins 4.0K ./upgrade-temp-backup

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.

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.

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.

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

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?