wolstech

Sent. Please check your email.

High server load. 3038.55 MB ... in 30 minutes. Oof. The limit is 1000MB per day, you managed 3 times that in half an hour. Wordpress is infamous for this, and is the leading cause of load suspensions. Plugins make it even worse. WooCommerce, Wordfence, and Elementor are 3 big offenders for plugins, but plenty of others will also cause it. I added deny from all to .htaccess to prevent it from running and unsuspended you. Do not run that WP install here again.

Changed. Please make sure to configure DNS by setting the name servers to ns1.heliohost.org and ns2.heliohost.org, or by setting A and AAAA records to the IPs shown in Plesk. The domain may take up to 2 hours to start working, and SSL will take several additional hours once the DNS is configured.

For SFTP, use the server tommy2.heliohost.org as the host, not your domain. Port is 1373, username is franklow and password is the same as plesk. I see you have a Lily account as well, if you're accessing that, Lily only supports ftp on port 21. SSH proper ( command line ) is not permitted as moneybroz already stated.

Moodle does not run well on our servers. It's too heavy and usually either throws errors or gets the user suspended for load. It's enterprise software and is designed to be run on a dedicated server, so a VPS would be appropriate for it. I'll let Krydos deal with the domains since removing a domain tends to delete its content and I'm not sure if there's a better way to make an existing domain the main domain without backing up, deleting it, then changing the main domain to re-add it.

Domain added. It may take up to 2 hours to start working.

@MoneyBroz I believe this user pays manually every 6 months vs. as a subscription.. The link shown in the admin tools is for the subscription payment. Krydos has to manually generate the links for one-time payments.

Krydos can do this for you.

I assume you're doing this in Plesk? If so, uncheck the option for wildcard certificate and try again. That option is what causes the DNS prompt and is not supported.

Deleted.

It's because you're using WordPress. WordPress is badly written and extremely inefficient. Most users on our service that try WordPress have this issue (and if they don't, they usually end up suspended for high load instead). You can try removing a bunch of extensions from your WordPress installation (some such as elementor, wordfence, and woocommerce are especially known for their performance impact), but the best solution is to use something other than WordPress.

Setting is intentionally set to prevent you from accessing files outside of your home folder. As said above, if you need this to be set to none, you'll need to buy a VPS instead.

Looks like it probably hasn't propagated yet then. Give it until tomorrow and try the test again.

Recheck name servers, still showing domain.com: https://bybyron.net/php/tools/dns_records.php?domain=ppblk.space&rec=NS also, the best you can possibly do is going to be about 7.5 until you get a different domain. -0.499 FROM_SUSPICIOUS_NTLD From abused NTLD -0.001 FROM_SUSPICIOUS_NTLD_FP From abused NTLD -1.725 PDS_OTHER_BAD_TLD Untrustworthy TLDs URI: ppblk.space (space)

It's because WP is badly coded software. This 504 error is one thing that can happen when the software is so bloated that PHP times out before it can finish running the Wordpress code. It can also occur during an Apache restart, but that usually goes away on its own within a few minutes. A stock installation is usually not too bad, but if you add any extensions to it, it becomes so bloated and slow that it usually won't run well if at all. Some extensions are worse than others, but Elementor, WooCommerce, and Wordfence are three that are well known to cause this. If you do get it to run with extensions, odds are you'll end up suspended for high load, which is what usually happens to people who use WP. People use it because its a well known name, but literally anything else is a better choice. As for the vulnerabilities showing on a new install, you probably need to update it after installing, especially if you install through Plesk since Plesk tends to have older versions in its software installer. Also, forgetting to update it regularly will usually result in a hacked account (and a subsequent ban when the hacker sets up phishing or sends spam).

Yes SPF and DKIM can be fixed for any domain since they’re just DNS entries, but the fact that that the domain ends in .space is in itself a problem (major providers have blacklisted a lot of these “vanity” TLDs like .space, .zip, .page, .xyz, etc. because that are prone to abuse). That can’t be fixed without buying a different domain that doesn’t end in one of those.

Still exists, but they only have a few TLD's now. The .ml and I think .ga are no longer offered.

You need to be using our name servers (ns1.heliohost.org and ns2.heliohost.org) for the records that Krydos set up to do anything. Also, one of the issues on that report is that the domain TLD .space is considered less than reputable. There is no fix for that besides buying a normal domain like a .com or .net and using that instead.

Working for me as well. I see a scheduled maintenance message from your site, not the default web page.

Krydos can do this for you.

Yeah that's the missing SPF and DKIM. Krydos can set this up for you.

Fixed. The DNS zone was missing. The domain appears to already be alive, but it will take up to 2 hours for the SSL to start working.

Krydos can cancel this for you.

High CPU usage. 10479 CPU This time it's for high load. You may need to see about optimizing your Joomla installation, or perhaps consider using Cloudflare's proxy function if you don't already. This topic has some information: https://helionet.org/index/topic/57606-handling-cpu-load-spikes-or-high-load-using-cloudflare/ (note that while some of it pertains to WP, the Cloudflare stuff should work on Joomla as well). Unsuspended. It may take a few minutes to start working.

A 344MB error_log and as well as a processed access_ssl_log for forum.mupdvig.tk have been removed. The messages were basically a flood of access denied errors from the IP of an abusive indexing bot. You can set up log rotation to prevent this. I've set it for you to no more than five 10MB files, but you may want to change it. To do that, in Plesk under the affected domain you can go to Logs->Manage Log Files->Log Rotation and set a max file size and number of logs to keep.