wolstech

The contents of ths.helioho.st have been discarded, and malware has been cleaned up in one of the other domains too (mac.php file again). 

I did notice that there are two additional WP installs on your account in agp.helioho.st and sai.helioho.st. Do you still need these? The agi domain doesn't even work (DNS issue), and you said you thought all of your WP was gone except ths, but it's not. There's still 2 more installations. If you're not using these, it would be best to delete the WP installs to ensure they don't get infected (or the entire domain if you're not using it at all). They are clean at the moment.

Also, this is the second time now that I've had to spend more than half an hour cleaning up your WP issues. If one of the remaining Wordpress installs gets hacked on your account, we're going to require a full reset without a backup, as it's not reasonable for me to keep cleaning this for you due to the amount of time it takes.

Unsuspended.

I'll get this cleaned up later this afternoon for you and post back when done.

Yeah WP as a technology is unfortunately junk these days. The more popular software gets, the more likely it is that it will become the target of hackers. WP is one of if not the most widely used CMS out there, so it makes a great target for cybercrime efforts. They can find one exploit and turn hundreds of thousands of websites into spam and phishing machines overnight...it's simply too big an opportunity for  cybercriminals to ignore these days.

This has been renewed. 

Quote

except the ths.helioho domain.

Yeah the ths one we left behind is now hacked too (it was clean when the last one happened). That WP install will need to go as well. Do you want me to discard the contents of that domain and check the others again?

Wordpress gets hacked on other hosts too, it's not unique to us. I've personally had it happen to sites I manage for people on GoDaddy and 1&1. Securing WP simply isn't worth the effort anymore. Cybercriminals have bots that can and will break into thousands of WP installations within a few hours of a new vulnerability becoming available (and you can bet those are being found via AI now too), long before any patches are available. Then there's the cybercriminals who release free extensions and themes for WP that come with a backdoor included so they can hack anyone who uses them.

If you take a look at your logs, I'll bet your other sites have tons of random IPs in their logs with failed requests for wp-login.php xmlrpc.php and similar WP-related files. Those are all bots trying to break into nonexistent WP installs...

Your error is this:

AH01220: Timeout waiting for output from CGI script /home/alphamarkt.helioho.st/httpdocs/cgi-bin/trading_bot_cron_test.py

Either your script isn't returning any output (it needs to send headers at minimum), it's not exiting (e.g. stuck in infinite loop), or the software is too heavy and the server can't finish running your code before it times out.

Domain added. It can take up to 2 hours to function.

It looks like that domain was already added to your account a few hours ago. You do need to configure DNS before it will work though.

Your addon domain has been converted to an alias. The changes can take up to 2 hours to function.

It sounds like you needed an alias, not an addon domain. An addon domain sharing a document root with the main domain is not recommended...doing so can cause issues in Plesk, and will completely break both domains if the addon domain is later removed (Plesk will delete the now-shared document root).

Do you want me to convert this to an alias for you?

That domain is working properly for me. No SSL error shown.

Is this still an issue?

I assume you're using $_SERVER['REMOTE_ADDR'] to get this value...if both the server and the visiting device support IPv6, it's typically going to be preferred. PHP can only see the IP of the connection used to call the script, so if the connection came in on IPv6, you'll see an IPv6 address.

Please remove the content within 24 hours.

Unsuspended. The account can take up to 2 hours for domains to work again.

You’re suspended for copyright infringement because your website was observed playing copyrighted music without a license.

Do you have a license to stream this music? And if so, can you please provide documentation of such license?

Subdomain added. You'll need to create an A record for the subdomain since you're using Cloudflare.

The domain can take up to 2 hours to function.

Duplicate request. https://helionet.org/index/topic/68427-i-need-to-add-domains/

Domains added. Please be sure to configure DNS.

The domains can take up to 2 hours to function.

This support request is being escalated to our VPS admins.

Our servers do look like they should support this...we've never had anyone ask before though. Escalating so the VPS team can look at it.

Backups must be unpacked on your computer, then the individual files and databases manually restored. We do not support automated restore of user-supplied Plesk backups. If this is a Plesk backup, the instructions for unpacking it can be found here: https://wiki.helionet.org/Account_Backups#How_to_Extract_Your_Account_Data_from_the_Backup_File

If it's a tar archive from the Johnny crash, you should be able to just open it in 7zip or a similar tool to extract the files, then upload them manually.

Just wait for him to respond here. Asking in multiple places usually just results in duplicate work and confusion for us.

Glad to see you got it working.

Please let us know if you need anything else.

Domain added. Please be sure to configure DNS using either our name servers or A and AAAA records pointed to the IPs listed in Plesk.

The domain can take up to 2 hours to function.

Domain added. It can take up to 2 hours to function.

Krydos can do this for you.

Alias added. Please be sure to configure DNS, either using our name servers (ns1.heliohost.org and ns2.heliohost.org), or by using A and AAAA records pointed to the IPs shown in Plesk.

The alias can take up to 2 hours to function.