Krydos

I was looking at the server reports, and happened to notice that your account is still using the most memory on the server. I also checked your files and I see that you're still using wordpress. I was already at my limit with your high load, and I wasn't planning on unsuspending your account again because our policy is three strikes and you're out, but wolstech is nicer than I am and he unsuspended you anyways for whatever reason. If you get suspended for high load from wordpress for the FOURTH time without making any attempt to reduce the load there are only three options left for you: 1. I delete wordpress from your account for you. You better make a backup quick so you don't lose anything. 2. You get moved to Johnny where your wordpress load won't affect our Tommy donors. 3. Your account stays suspended forever, and you can find another host. You said you would fix this "in a few days". It's been a week. This is your last warning.

You may not know this already, but wordpress causes massive load on the server. High load from wordpress is the most common reason for people to get suspended. Switching to anything other than wordpress would help immensely.

Unfortunately, as you may know already, Tomcat uses massive amounts of memory, and the more accounts have access to it the more memory it requires. Our servers obviously have a finite amount of memory so we cannot allow every single account that signs up to have access to Tomcat. The way it works then is there is a waiting list, and when someone else stops using java the next person in line gets access, and the total number of accounts with simultaneous access is kept at a reasonable level that the server can support. If you signed up right now with 1 account and requested java access the estimated install date for that 1 account would be 2020-08-20 (16 days). That's just an estimate though based on the historical rate of installs over the last month or two. The actual install date could vary plus or minus depending on whether anyone stopped using java. As long as you're still using it actively you can keep access forever, and some of our users have been hosting java/jsp websites for years without giving up their access. Since only 1 account at a time is granted access when the server can support another account it could takes weeks, or maybe even months for all 50 students to get access on each of their 50 accounts. Also, as you already noticed, our free service is more popular than we can support with our limited number of servers, and limited budget, so we have to limit the number of new accounts that are created each day to keep the servers operating at a reasonable performance. Only two server plans have java/jsp available: Johnny and Tommy. We allow the most number of new accounts each day on Johnny so he is the most overloaded, has the worst uptime, and is the slowest, but signups stay open longer each day. To give you some numbers, yesterday Johnny was available for 4 hours and 10 minutes. The day before 3 hours and 53 minutes. The day before 12 hours and 33 minutes. The day before 3 hours and 25 minutes. Tommy also has java/jsp access available, but in order to keep him fast and have a good uptime we restrict the number of new free accounts each day to prevent him from becoming overloaded. Tommy is also the most sought after server because of the better quality. Yesterday free Tommy signups were open for 0.561 seconds. The day before 6.308 seconds. The day before 2.033 seconds. The day before 15.307 seconds. Tommy free signups rarely last longer than 10 minutes, and are usually less than 10 seconds. We also offer the option for donors to create an account on Tommy at any time of the day they want, even if the server is full for the day. I don't know if it would be feasible for your students to all take turn using one account? Another option you might consider is getting a vps for a few months or however long you need and installing tomcat on that. We offer scaling vps that can go as high as 32 GB of memory, 300 GB hard drive, and 8 cpus. We've never done it before, but I'd be willing to give you a trial to make sure it will work for your class and then even a discount off our advertised price since you're using it for education. You can check out the vps options we offer at https://www.heliohost.org/vps/ Thank you for considering us for your class. We've been offering free web hosting since 2005 and we've always tried to help people learn. A few people have even come back and let us know that what they learned while using our free service kickstarted their entire career, like this guy https://www.helionet.org/index/topic/15738-heliohost/ Let us know if you have any other questions, suggestions, concerns, or need help with anything else.

Pycocotools is not compatible with our free hosting, and torch is 750MB. While I was trying to install torch pip almost crashed the whole server because it was using so much memory. I think you need a vps https://www.heliohost.org/vps/

The login page, and the new website in general, accept username or email. The old website, and the account deletion page only accept username. If you were using your email address as your username in this form that would explain why it didn't work.

I did a little more research and it turns out to start a php script with popen you need to set shell=True, but that isn't required with python scripts. I've never started a php script using cgi like this so I didn't know that off the top of my head. I edited your start.py and tested it and now it works. The other issue I found was your stop.py script has to search for ea-php72 instead of websocket_server.php because php is the executable and the script is an argument passed to the executable. Once again I made the change to your script and tested it and it's working. I don't know how to test your socket though. I left the script not running, so open the start script in your browser, and then test out the socket to see if it's working. Let us know if you need any additional assistance.

This happens sometimes when someone installs a broken ssl certificate instead of using autossl. Usually it's a cloudflare certificate, but this time it was a sectigo. Once that certificate is deleted apache will restart on it's own again. This only ever happens on Ricky though, so there must be some error checking in newer versions of cpanel that prevent the whole system from crashing from one screwed up certificate. Anyways, it's been unstuck. Thanks for noticing.

Your account was archived not suspended. Suspended implies you violated our terms of service. Archived just means you didn't log in for a long time. Unarchived.

Unarchived.

The country >>>IS<<< the problem. The governments in the countries that see this kind of rampant illegal activity do nothing to prosecute the criminals, and in some cases go to great lengths to protect their criminals. Correct. All countries have good and bad citizens, but the reason you don't see this kind of abuse from US, Canada, UK, Australia, etc. is because their governments are willing to prevent these kinds of crimes. If Nigeria and Indonesia would actually throw these people in jail it would scare the rest of the criminals into behaving like reasonable humans.

Are you using python2.7 or python3.6?

The next issue I see is that file isn't executable on its own. You need to make it like you did in the cron subprocess.Popen("/usr/local/bin/ea-php72 /home/roguitar/public_html/chat/server/websocket_server.php")

It's hard to say for sure what the issue is with so little information, but since you picked the Johnny server it could be high load or downtime. Johnny is our experimental server, which means he's only suitable for experimenting on. If you need a fast website with high uptime we recommend Tommy. To give you some numbers, for the last week Johnny has had 90.91% uptime, and Tommy has had 99.89% uptime. That's quite a difference, and could explain seeing errors like that roughly 10% of the time on Johnny.

Remote access enabled.

The power outage was 43 days ago. I don't see how that could have anything to do with your site today.

The account habarly has been unsuspended. Let us know once it's deleted and we can unsuspend the other account.

Unarchived.

Unarchived.

You took too long deleting one. Now only one can be unsuspended at a time. Which one do you want?

We strongly recommend not using wordpress for this and many other reasons. Wordpress is really bloated which means it uses a lot of memory which results in a lot of those out of memory errors. If you refuse to get rid of wordpress you could try disabling plugins that you don't need. Most free wordpress plugins are just backdoors for hackers to set up a phishing site on your domain anyways. Also, I recommend using the latest version of php which is 7.3 on your server. Php 7.3 on Johnny has a 64 MB memory limit, where as php 7.2 on Johnny has a 32 MB memory limit. Switching to anything other than wordpress is the best solution though.

You'll have to use whatever backup you may have taken prior to the hacker getting access. We can't allow you to have any information from the hacked account because we may as well be giving out stolen credit card numbers, etc. to you if we were to unsuspend it for you. We're holding the account as evidence for law enforcement.

Remote access enabled.

First of all, you keep mentioning that you donated $1. Some of the people on Tommy have donated $500, so do you think it's fair to them for your account to cause downtime for their website? Since we've given you 3 chances already to fix the issue, and you have failed to do so I'll provide some options for you. Please pick whichever option works best for you: 1. Stop using wordpress entirely as Wolstech instructed. 2. Convert your wordpress install to a static site using something like this https://hostadvice.com/how-to/how-to-convert-a-wordpress-site-to-a-static-html-website/ 3. Purchase and move your wordpress site to a vps where your load won't affect the other thousands of users. https://www.heliohost.org/vps/ 4. Agree for us to move your account to Johnny. Please let us know your decision as soon as possible.

I had it as pophead for some reason. I don't know where the s went. Must have been a copy/paste failure. Try now.