Krydos

Please take a look at https://tommy.heliohost.org:2083/frontend/paper_lantern/load/index.live.php

High memory usage coming from php 7.2. Have you considered a VPS? You may have outgrown Tommy.

Then why did you use his email address to register your account?

Have you tried resetting your password with this link? https://www.helionet.org/index/index.php?app=core&module=global&section=lostpass

Do you have more than 1 account?

Unarchived. You'll need to reset your password before you'll be able to log in.

The problem was someone else moved you back to Tommy. The account transfer tools weren't designed to enable java after being moved.

Moved. Thanks again.

I enabled remote connections to the database calkarob_first_test from the user calkarob_first_user.

Unblocked.

The way this works is Tomcat is ridiculously memory hungry. The more people we grant access to Tomcat the more memory it uses. The server has a finite amount of memory so obviously there is a finite number of accounts that can have java active at any time. There are several ways to lose java: 1) Say you don't need it anymore. Don't hold your breath for this one. I think it's happened once in the 10 or so years that we've been providing java hosting. 2) Account goes inactive from lack of logging into cpanel. 3) Account is deleted. 4) Account gets suspended for something. 5) No java traffic for a substantial amount of time. Obviously we can't just know when one of the above conditions is going to be met so the best estimation we can do is simply figure the average amount of time each person waited to get java access and then multiply by the number of people ahead of you in line. That said, Tommy is still a rather new server, and we're still getting everything balanced. We were having some pretty serious load issues, and since Tomcat is one of the biggest contributors of load on a server I tightened up the restrictions and transferred a few accounts off Tommy entirely to help balance the load out. Now that Tommy is doing better overall I have already begun loosening the restrictions slightly to allow Tomcat to cause a little more load. As long as everything stays balanced this will mean more people will be able to have java access at once, and the wait time will go down. So, like I said on discord I don't expect it to take until February for you to get Tomcat access. If you'd prefer to move to a VPS and have Tomcat access immediately I'm willing to put your Tommy donation towards the price of a VPS which start at $4 per month, and I can help you set everything up too if you need help.

$4 per month is the current lowest price VPS we offer.

Yeah, all wordpress load just comes from index.php.

Unarchived and renamed.

Remote access enabled.

It should be available already.

Remote access enabled.

According to what he said on discord he didn't like the .xyz domain anyways, so he bought a .site instead, and instead of using Tommy he's already paid for and is using a VPS.

The account adminga is now fully deleted.

Remote access enabled. Sorry for the delay getting this done. No one flagged this topic with [Krydos] so it slipped through the cracks.

If the phishing report was also sent to his domain registrar it's possible they suspended his domain, in which case he'd have to contact his registrar's support.

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

For anyone who is curious or finds this thread through searching, the difference is the cpanel version. Tommy is running the latest version of cpanel and Ricky is running a much older version. In the older versions of cpanel the optimize website button in cpanel enabled .htaccess mod_deflate compression on all static files, and also enabled zlib compression for php too. In the newer versions of cpanel like Johnny and Tommy have and Ricky will one day be upgraded to the optimze website button in cpanel only enables the compression on the static files. In order to enable php compression an admin has to do it. That's why there's the note in cpanel about contacting your system admin. I'm not sure why they made this change. It actually seems better to me in the older versions of cpanel.

This should start working within an hour or two. Let me know if it still doesn't work. In the meantime it may show a 404 error or a queued page.