Krydos

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

Your site isn't queued, but it does have a 500 error. The leading cause of 500 errors is wrong permissions. Please make sure your php files have 644 permissions. A lot of the time FTP clients upload files with 664 permissions which results in 500 errors. Also we strongly recommend you don't use wordpress. It causes a lot of load, which could get your account suspended, and it is also very insecure, which means a hacker can easily gain access to your account and set up a phishing site on your domain or send spam emails, which would also result in your account being suspended. Literally any other software you could install on your account is better than wordpress.

What php version are you using?

The best way to fix this is to edit your scripts to use /home/tstamp/tmp instead of /tmp. That way if something goes haywire you only take out your own account, not the whole server.

Your account used over 2.1 GB of space on /tmp and caused several hours of downtime for the thousands of other accounts on our best server. That's why you were suspended.

You'll need a VPS for most of that. It can't be installed on a shared hosting account. https://www.heliohost.org/vps/

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.