wolstech

Reset the password here: https://www.heliohost.org/reset/

Did you make the file permissions 755?

You're on Tommy now. Thank you for the donation

Unarchived.

Donation verified. I'll move it shortly.

Make sure the files have unix line endings. If you made the files on Windows, they won't work unless you use an editor that lets you specify unix style line endings (Notepad++ can do it).

You'd need a VPS for that, and a very large one at that (especially CPU and RAM). https://heliohost.org/vps/ You'd need 4 cores and at least 4 GB of RAM, 8GB or more if you plan to have more than 2 or 3 players at any given time. I've run two myself (1.7.10 and 1.16.1), and they're by far the most resource hungry game servers I've ever hosted.

Start by trying another device on the same network (e.g. your phone while on the same Wifi). If that works, then you probably have a firewall on your computer blocking it. If that doesn't work, your router may be the cause.

Unarchived.

Port 2083 is blocked on your computer for some reason, which is very odd for a home computer. Also, please keep in mind that the link you're using won't count for the inactivity timer. You'll need to log into our website to keep the account active, even if you open cpanel itself using that link. (For what it's worth, the "Insecure login" link on the heliohost tools page on our website should be the same exact link as the one that works for you). Krydos has to install postgis. You can't do that yourself.

Does either of these links work for you: https://tommy.heliohost.org:2083/ or http://cpanel.tommy.heliohost.org/ ? It's not showing as blocked in the firewall on our end. If the above links don't work, let me know and I'll have one of our other root admins look at this.

This request was forgotten about. Sorry about that. Unarchived.

Are you logging in from a workplace or school? That's the most common issue, and it's caused by your organization blocking port 2083. Try using the "Insecure Login" button at the bottom of the tools page instead. This logs you in via unencrypted connection on port 80, which should work pretty much anywhere.

Hosting account usernames (the actual cPanel username, not the domain) do require a delete and recreate. Forum usernames can be changed. Since you just wanted a domain change, we could've just changed the domain on the existing account.

I just cleaned out a bunch of garbage from /tmp. Most of the crap was WordPress updates and imagick temps.

The immunity is a single extension from the date of donation. It's NOT a permanent thing (e.g. "must log in every 90 days"). If you donated for 3 months worth in October, it would've expired sometime in January. Once it expires, you have 30 days from the date of expiration to log in. Example: If you donate for 3 months immunity on October 10, immunity would be good until January 10. From that point, you have ~30 days (until February 10) to log in. If you don't log in before February 10, you get suspended for inactivity.

Unblocked. I would need the IP of the gitlab runner in order to unblock that. Without it, it will unblock on its own in time (there's a max number of IPs that can be banned at once, so as time passes, usually a few days to a week or two, it'll just fall off the bottom of the list on its own).

Yes Softaculous could've made those changes. A lot of forum software comes with a custom .htaccess designed to secure the forum software, however if other apps share a domain with it, they often need to be modified to make them compatible.

Yep, line endings will cause all sorts of weird issues with Python. You need to make sure they're unix style

It has to be completely rewritten to fix it since the current script uses an API that hasn't been supported by WHM in years. It'll happen eventually. As of now, it still works as long as the new domain is not a .heliohost.us domain (so you can change it to your own domain just fine, you just can't assign yourself one of our subdomains at the moment). Now...I can't change his domain because I can't find his account...

Your .htaccess files are causing this. I renamed them to htaccess.old and its working. Specifically, you disabled directory listings in the .htaccess file, but didn't provide an index.php for those domains. If there's no index and you disable directory listings, you get a forbidden error.

@Seekier: that script doesn't work for the heliohost.us subdomains. I have to change them manually in WHM. I'll take care of this later this morning when I'm at a computer.

Unarchived.

Done.

Unarchiving...