wolstech

That meta tag will cause an infinite loop. The PHP method is what I use. It's a nice choice because it lets you still access other files on the server over plain http if necessary without adding a bunch of exceptions for them, but the average joe visiting your site will still be given an https connection.

Cloudflare and AutoSSL cannot coexist on our servers, so you may find yourself manually installing certificates if you use CF. Tommy is fast enough that you really don't need it anyway to be honest. It won't make much of a difference anyway unless you have lots of big pictures or something on them. It won't even help the speed of dynamic pages (php, etc.) because the scripts have to run every time they're visited. CF is more useful for Ricky and Johnny where the servers are painfully slow even for static content. Also, when troubleshooting this sort of thing, it's best to forget about forcing https entirely and just get the site to accept the connection. Rename the htaccess and get everything else working first.

Seems to have resolved itself, now reporting 80% full.

@sohamb03: Doing that will break AutoSSL because it won't be able to renew when the cert expires. It either needs an exception added for .well-known, or he add a redirect in index.php instead of using .htaccess.

Looks like Tommy's /tmp is full...lots of applications throwing No Space Left on Device when trying to save into it at the moment. If anyone has applications that are suddenly throwing unexplained 500 errors, especially during file uploads or database operations, this is the likely cause. The errors will correct once the space has been freed.

Yep. Apache has to restart before SSL will function after the certificate has been installed.

This comes from the linux / Windows divide. In Linux, upper and lowercase are considered different (TableName != tablename != Tablename), whereas in Windows, its practice to ignore case entirely (TableName == Tablename == tablename). Filenames and such are the same way. You built an app for a linux server using the Windows conventions from the sound of it. Tables are actually stored as files, so they follow the file system convention. The columns inside follow suit. See this: https://stackoverflow.com/questions/2009005/are-column-and-table-name-case-sensitive-in-mysql Sadly it's time to edit everything for consistency. I had to do the same with my first ever program as well. Any linux based host you use will have a similar requirement.

You could download composer on your home PC and run the commands there. It'll build the forum software and save the files in a folder of your choice. Then you can just upload that folder of files here. I'll move this so Krydos can respond if he has any other suggestions.

Krydos (like the rest of us) isn't around all the time. We're all volunteer and have a real job and life outside of this place. He usually stops by once or twice a day. The account is acting quite strangely considering you can log into it. If it was really suspended, you wouldn't be able to do that.

Done. You can now log in, and the domains will start working when Apache next restarts.

Unarchiving...

Done. You can now log in, and the domains will start working when Apache next restarts.

Unarchiving...

@Byron: That account is in fact showing a suspended page despite not being suspended...

Passwords will report incorrect for any server that's down simply because they can't be checked. However, there's a second issue currently as well with Tommy when it comes to account management. @flazepe: Take a look in the admin tools and you'll see our account system has absolutely no idea what the domains and emails for half of Tommy's users are... Because of that, the heliohost.org login might not work for those users simply because it can't resolve the email address to a username. These users can still sign in by using their actual username and password, though they might need to use https://tommy.heliohost.org:2083/ until the issue is fixed (my account isn't affected or I'd test it...)

@sohamb03: No I don't. The only times I've even seen that account mentioned are in system logs and exim queues.

From my understanding, heliohost2 is an email account where a bunch of system alerts get sent. I'm not sure exactly what it's used for otherwise (or who if anyone even checks it), but I know I've seen various cpanel alerts waiting to being sent to it when I check the exim queues on the hosting servers.

That account is not suspended.

If you visit the page in cpanel where you request it, it should give you the estimated date you'll get it. Most users actually get it sooner than that date if they're on Johnny. Tommy accounts may actually take longer.

Did you request java and wait? Java is not enabled by default, you have to request it and there’s a several week wait for it due to demand. Also, other things to consider...Java and CGI are not the same thing. CGI is for things like Perl or Python. Also, Java does not support HTTPS by default.

You probably need to clear your cache. That account was configured yesterday. As for testing it, I can't at the moment because Johnny is down from load again...

Java only works on plain HTTP by default. It's possible to have it moved to HTTPS, but then plain HTTP won't work...you can't have it both ways unfortunately because doing so would mean the account would hog two Java slots.

@sohmab03: It's only because of the fundraiser that he can get an increase on top of an increase. Normally you'd be correct.

Johnny is a bit behind on his Apache restarts at the moment due to his load being extremely high. When it restarts next the domain should start working.

Please change the domain's name servers to ns1.heliohost.org and ns2.heliohost.org, then add the domain under Aliases in cpanel. After that it should work within 2 hours of completing the steps.