Krydos

The offending account has been suspended and his files deleted.

Remote access enabled.

Unarchived.

Remote access enabled.

Unarchived.

There you go https://krydos2.heliohost.org/cgi-bin/modules37.py

Yep, Johnny's php 7.1 already has mbstring installed https://krydos2.heliohost.org/71/phpinfo.php

Remote access enabled.

Unarchived.

You get a 404 because you're redirecting to something that doesn't exist. There is nothing at https://mario-kart.billigerkaufen.com/

Just use MutliPHP to set your php version to 7.2. All php versions on HelioHost come with mysql and rewrite so you don't need to worry about those.

I'm curious how something like this would work for our wordpress people https://hostadvice.com/how-to/how-to-convert-a-wordpress-site-to-a-static-html-website/ You could then put a 403 forbidden on the dynamic, slow, buggy wordpress site unless you were actually adding new content, and let all the traffic go to the static site that can't be hacked, is much faster, and causes basically no load.

Before we go much further I need to give you the standard wordpress lecture. Wordpress causes insane amounts of load. Your site has only gotten 164 MB of traffic over the last week and already it's topping the charts on load for the server This is very common for wordpress. Wordpress is the #1 cause of high load suspensions. If your cpu or memory bars reaches 100 it means you could be suspended at any minute. If your site can reach #1 cpu on a server that hosts thousands of other accounts with only 164 MB traffic for a whole week imagine what the load will be when you actually start getting traffic. For comparison, the #1 bandwidth account for the week transferred 12 GB of traffic, that's 73 times as much traffic as your site, and your site used 6 times as much cpu as his. Just some numbers to consider. We always strongly recommend people don't use wordpress for this and many other reasons. You can keep an eye on your load graph at this url https://tommy.heliohost.org:2083/frontend/paper_lantern/load/index.live.php

Try this RewriteEngine on RewriteCond %{HTTP_HOST} !america.mysite.com RewriteRule /test-page/ https://america.mysite.com/test-page/

Unarchived.

I can usually get better python error logs than cpanel provides. They leave out a lot of info and stack traces. If you want me to provide logs for something you'll need to tell me the full url. Right now there's nothing in your public_html directory so no logs.

Sure, put this line in your .htaccess Options -Indexes With that it will show 403 forbidden if you don't have an index file.

Does port 587 work?

Those settings look right to me, and I tested SFTP with Flezilla so it should work. Can you enable more detailed error logs in Filezilla and post the log? There's actually two problems that I see with your cgi. First, your file is encoded with DOS line endings. Our servers run Linux so using DOS line endings will result in a 500 error. This is usually caused by writing the file with a Windows editor like notepad, and then uploading the output. There are two easy ways to fix this.Use a Windows editor that understands and can write Linux line endings. I've never used it, but I've heard that Notepad++ has this option.Create the file and copy/paste the code into the cpanel file manager.Secondly, you're on Ricky which has python 2.7 and python 3.6 available. Your shebang is python 3.7, which would work on Tommy and Johnny, but on Ricky you need to use /usr/bin/python3.6. Trying to use a binary that doesn't exist would also result in a 500 error. Generally it takes less than 24 hours to get it all set up for you.

I have tested SFTP on Ricky, and can confirm that it is working correctly. Try these settings: SFTP host: ricky.heliohost.org SFTP port: 1312 SFTP protocol: SFTP SFTP logon type: Normal SFTP Username: smi93ctb SFTP password: <same as cpanel>

Port 465 for SMTP means you're using SSL. Tommy's used the same SSL certificate for over 300 days. Yesterday I found out that Tommy's year long SSL certificate was partially invalid because it was signed using that root certificate that expired on May 30th. It actually caused an issue with a mail script of my own not being able to connect to Tommy anymore even though tommy.heliohost.org in a browser wasn't showing any errors. I updated Tommy to use a new valid certficate issued by Let's Encrypt. You can see that the SMTP certificate is valid with this link https://www.sslshopper.com/ssl-checker.html#hostname=tommy.heliohost.org:465 If you can't make your script work with the new SSL certificate you could try without SSL/TLS on port 587.

Create a /home/trbot/public_html/.htaccess file and put these contents Options +ExecCGI AddHandler cgi-script .py DirectoryIndex index.py The first two lines make .py files executable outside cgi-bin, and the last line makes the filename index.py show up if someone goes to domain.heliohost.org without having to type out the filename like domain.heliohost.org/index.py

That's odd because the script's changelog says it's compatible with php 7.3 Version 1.7 (31st January 2019) - Now compatible with PHP 7.2 & PHP 7.3

Your domain, cuted.tk, is available to register at dot.tk. It's not going to work until you register it with them. Once you register it be sure to set your nameservers to ns1.heliohost.org and ns2.heliohost.org. The other option is you can change your domain to something.heliohost.org with this script http://www.heliohost.org/classic/support/scripts/domain For instance cuted.heliohost.org is available. If you use one of our domains you won't need to worry about nameservers.

It said it was inactive in the system and I was able to renew it for your using https://www.heliohost.org/renew/ I think Wolstech said it takes a few minutes to sync up after a Lily account is reactivated. My guess as to why this happened is probably because Lily was online, but our main system database on Cody was offline.