wolstech

Rename .htaccess so its ignored and see if the 500 error goes away. If so, its a syntax error or unsupported option in .htaccess. Also, remove the "force http" section, the services that need the stuff in .well-known will use whatever protocol they please and tend to hate being forced onto a specific protocol. AutoSSL likes HTTP, but there's also stuff that likes HTTPS in there. Let the services themselves use what they want, don't force anything. The size of your page doesn't matter since we don't monitor bandwidth unlike other web hosts. It's the amount of CPU and RAM on the server that we monitor, and WP is simply the worst at both of these. You're topping our charts with just your test traffic, and CF won't fix that because dynamic pages are not cached by CF. Other hosts generally monitor bandwidth instead of resource use, because it's easily quantified and they have tons of servers that they can pay for with money from paid hosting. Since we don't have paid services and also don't pay for bandwidth (our provider gives us unlimited traffic), we control the server resources instead so we can pack more accounts into a single server. Some other things to consider: SSL is increases load, as does compression (if you use it). The only real fix is to not use WP, but not using SSL (from a security standpoint it's pointless unless your site collects information of some sort anyway) and turning off any sort of compression you have enabled might help a little. Krydos's idea looks promising too. Convert the public site to static HTML and only use the WP install to generate new static pages when you change content. Static pages cause virtually no resource use at all. Once live, that site will end up suspended if the numbers above continue.

Most notably, its a security disaster. WP gets hacked regularly, unlike just about every other CMS in existence. Once hacked, the hacker usually either sends a bunch of spam or sets up phishing. Either way, WP getting hacked will usually earn your account a permanent suspension and loss of all data. WP is the #1 cause of accidental suspensions here at HelioHost. If you need an alternative, Joomla (and more recently Ghost) have been quite popular around here and they don't suffer these same issues.

First, the forced SSL prevents the server from getting a certificate. There needs to be an exception so the .well-known folder can be accessed via plain http. I don’t have that code handy at the moment since I’m on mobile, so the crude fix is to just delete these two lines: RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}{REQUEST_URI} [L,R=301] ...and wait for autossl. That SSL error is normal when the cert is either missing or doesn’t cover the domain you’re using it on. Note that a cert for example.com will NOT cover sub.example.com. AutoSSL should get you the right cert if you let it, but it probably failed because you forced SSL. Also, it can take time to work, it’s not instant.

What language are you using? Java is the only one we would really have logs for. Python errors usually appear in cPanel under error logs, and php will produce an error_log file in the folder where the script is.

Can you try changing the hostname to tommy.heliohost.org and see if it sends? The server's domain is the officially supported domain for mail and should be used for other reasons anyway, most notably Tommy reports itself as tommy.heliohost.org when another mail server connects to it, so using that domain to reach it is preferred. If that doesn't work, I'll have Krydos look at it.

Indeed. A boolean false from a failed database query to Cody will cast to int 0, or a datetime of 1970-01-01 00:00...and Lily reacts by thinking your account has been abandoned for 50 years. Lily works fine, but struggles with error conditions. Also, please be aware that Lily is running maintenance tonight and has to do 6 months of backlogged updates. There will be a 10-30 minute downtime for the reboot at some point between now and 6AM EDT tomorrow.

It runs on PHP 5.6 under Windows (XAMPP) on my home PC perfectly too. It has something to do with the configuration of Tommy at this point. Try PHP 5.6 as I suggested, and if that doesn't work, we can consider moving it to Lily since she runs Windows.

Try PHP 5.6.

What version of PHP are you using? That gibberish could be mbstring missing...

Try reuploading first, but if that doesn't help, It's probably a compatibility issue of some sort. I assume your home PC is probably running Windows? Also, what are the requirements for the software?

Taking a look at the account, i agree, it looks like warez. @mithian: you have 24 hours to remove it or you'll be suspended for copyright infringement.

Luigi probably doesn't know that email suspensions have to wait until the mail counter resets before they can be unsuspended. You'll need to wait until at least midnight UTC.

Krydos can install that extension for you.

What version of PHP are you using ?

His port number is indeed wrong. 1342 is the correct port for Tommy (the 1373 he lists is for Johnny).

If it's just for disk space, you can buy an extra 1GB for $5, for a maximum 2GB for any one person. Since your donation is $5, I can just make the existing account larger instead

Unarchived.

Unarchived.

You can't get an invite because you have a Tommy account already (the account tstamp appears to belong to you based on the domains and content). Users are limited to one account maximum.

Does plain FTP on port 21 work? Sometimes SFTP has weird issues.

The picture seems to have gotten lost. Are you using FTP over TLS (if so that's not supported, you need to use SFTP instead)?

What IP is blocked? The one you posted from is not. Also, Webdisk is notoriously buggy. I'd suggest SFTP instead, it's much more reliable.

Do you mean the button never lit up to click, or it doesn't do anything when clicked? The first is usually an issue with the data you entered. Note that since you have a forum account called heirloom, your hosting account cannot use that username unless the email address matches the forum account. Second, we usually recommend a chrome-based browser (Chrome, new Edge, Brave, etc.). If continue to have issues, you should try signing up in an incognito window (which will ignore your extensions and cache), and use entirely new information. We can change your domain later if that's an issue.

If use use FTP, this error means the permissions on the file are set to 664 (note the center number is 6). They need to be 644 (center number 4).

Unblocked. It may take 10 minutes to be effective.