Krydos

Tommy is on django 1.11.6 https://krydos.heliohost.org/cgi-bin/modules36.py and we're not going to be downgrading to 1.9.

There you go https://krydos2.heliohost.org/cgi-bin/modules36.py

/home/alirezac/public_html/poinno.com/index.php It's wordpress causing the issue. No one is surprised. Probably 95% of our high load suspensions come from wordpress. As an example Maicol07 was recently having tons of issues with high wordpress load as well, and when we finally convinced him to ditch it he went from #1 load to #40 with the same amount of traffic. You won't find many wordpress fans in these parts. Please fix it. Unsuspended.

Well, that's bizarre. The index.jsp file is showing up on the server now, but it still gives the 404 error. I would recommend starting a new project with a different name in Eclipse like Wolstech suggested and see if it has the same problem.

In the servlet guide you have to manually create it too: Source: https://wiki.helionet.org/Java_Servlet

We can test it on your account if you want? I could edit your last logged in date and you can try logging in various ways. Let me know if you want to try. I suspect it was just a fluke. Perhaps the communication between Tommy and Cody was temporarily disrupted. The script that updates the last login date has no fallback if there is an error, nor does it test to see if the last login date was actually updated. It just sends one request to update the last login and then goes about it's business doing other things. If there were a lot of people having this issue I would be a lot more concerned. Most people that have issues with their login dates counting are logging in with a url like tommy.heliohost.org:2083/sess0000/frontend/paper_lantern/something/that/ends/in.html which will never work. Maybe Wolstech can recall if anyone has had an issue with https://www.heliohost.org/login/ before?

I just tested logging in on a Tommy account at https://www.heliohost.org/login/ and it updated the last login date.

The main issue is a DDoS attack http://heliohost.grd.net.pl/monitor/archive/?2018-07-11 but the high load from the attack seems to have crashed apache as well. I've got apache running again. Hopefully the DDoS attack has ended too.

If your email had this link in it it means you missed the warning email and your account was already suspended for inactivity. The two day warning email links to https://www.heliohost.org/login/

There is still nothing on the server.

root@tommy [/opt/tomcat/live/webapps/stockdi1_MyHelioServlet]# ls -la total 4 drwxr-x---. 4 nobody nobody 35 Jul 11 16:49 . drwxr-xr--. 27 nobody nobody 4096 Jul 11 16:49 .. drwxr-x---. 3 nobody nobody 54 Jul 11 16:49 META-INF drwxr-x---. 4 nobody nobody 44 Jul 11 16:49 WEB-INF root@tommy [/opt/tomcat/live/webapps/stockdi1_MyHelioServlet]# Still don't see an index.jsp.

That account cannot be unsuspended.

Mcrypt is available on php 5.4, 5.5, 5.6, 7.0, and 7.1, but not 7.2. http://php.net/manual/en/migration71.deprecated.php

Does it work now?

Which version of php are you using?

You still don't have an index file. See https://wiki.helionet.org/Java_Servlet#Create_index.jsp for an example index.jsp.

What does this .war do on your development set up?

Please don’t post your database password. Context.xml goes in META-INF. You can put it there yourself.

You can only have it enabled in one domain at a time. Enabling it on two domains takes up two slots which causes twice as much server load. The default is your main domain.

http://lucasgv.com/ is working now.

http://wildabyss.heliohost.org/ is working now.

Remote access enabled.

There you go https://krydos2.heliohost.org/cgi-bin/modules36.py

There you go http://loretojr.heliohost.org/test.aspx @wolstech, that error probably just means there was already an httpd.conf rebuild in process so it couldn't edit the file. It would then just pick up the changes the next time httpd.conf is rebuilt.

It looks like it deployed http://tssinfo.heliohost.org/savemytime/