Krydos

Suspended accounts do still cause a little load, but only like 1% of the load they would cause unsuspended. Still if someone on our servers gets the reddit hug of death suspending the account will help some, but not enough. The few times that this has happened I've actually had to delete the offending account's dns records, and after a few hours when the cached A records dropped off the internet the load finally came down to allow the other thousands of domains on the server to return to normal. The moral of the story, if your site is going to make it to the front page you should probably be using a VPS, not shared hosting. Even paid shared hosting would probably suspend you to get everyone else's sites back online. The chart updates once an hour, and the days are broken up based on 00:00 UTC. So at 01:00 UTC your current day's bars will show your load for the last hour, at 02:00 UTC your current day's bars will show your load for the last 2 hours, and so on. I've gone to great lengths, and spent a lot of time developing this load system to be as fair as possible. A lot of other hosting companies just suspend you if you go over X amount of memory used. This is silly though because if the server is fine, and everyone else's accounts are still online and fine why does it matter if one account crosses an imaginary line? Our system a popular account can sometimes cause massive load that any other hosting company would suspend for sure, and be fine. The downside to our system is it tends to cause some confusion because people have a good day like that with, just making up some numbers to illustrate my point, say 5000 people viewing their site or whatever and don't get suspended. Then they have another day where only 4000 people visit their site and they get suspended for it, but the second day with less views happens to coincide with 15 other accounts also getting 3000 page views causing the whole server to get overloaded and performance to drop for everyone. The first account is still causing the most load on the server with 4000 views, but they might not understand the bigger picture of the whole server. The reason I got upset is because our system can be a little confusing for users, I totally understand that, and your comments are just making it even more confusing to people, and making it seem even more unfair. Does that make sense now?

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

Pick a port that isn't already in use, like 4000, and use cgi or cron to start your script running listening on that port. Then use something like this to redirect requests to that port RewriteEngine on RewriteRule ^socket/(.*)$ http://127.0.0.1:4000/$1 [P,QSA,L] Then if you go to olimppius.heliohost.org apache will handle the html/php, but if your requests go to olimppius.heliohost.org/socket/(.*) it will be proxied to the internal port 4000 where your script is listening. Please be aware that port 4000 will not be accessible directly. For example olimppius.heliohost.org:4000 will just time out because the firewall will block it, but the firewall won't block internal ports between apache and your script.

Those two lines are examples of static content, or in other words content like imgaes that won't be passed through and processed by flask.wsgi. You can delete those two lines or rename media to static or whatever if you prefer.

I have no idea why you would say this. The numbers don't lie, so I don't know why you would lie to users about this. If you continue making things up we may need to discuss this further. This is the second time I've seen you spread blatantly false information, and who knows how many people you've told this to on discord. Your suspension shouldn't come as a surprise. We provide a tool in cpanel so you can monitor your own account load. As you can see you're one of the top memory usage accounts every day except the day that your account was suspended. To be honest the blue bars (cpu) don't matter as much most of the time. It's the red bars (memory) that will get you suspended easily. If you weren't aware of this graph you can check it yourself in cpanel at https://tommy.heliohost.org:2083/frontend/paper_lantern/load/index.live.php

Try adding the domain now.

What do you mean? Python is available to all accounts on all of our servers without any setup.

You can do sockets through port 80/443 if you use .htaccess to rewrite. If you'd rather have ssh command line access and the ability to open any ports you want you'll need a vps. https://www.heliohost.org/vps/

Here's the current breakdown root@tommy [/home/wbdvsm]# du -h --max-depth=1 936K ./.cpanel 0 ./.htpasswds 21M ./tmp 0 ./public_ftp 564K ./etc 4.4M ./mail 36K ./.spamassassin 360M ./public_html 3.1M ./.cphorde 464K ./ssl 172K ./.softaculous 0 ./.pki 0 ./cache 16K ./.subaccounts 1.6M ./logs 52K ./.razor 0 ./.trash 391M . tmp can probably be cleared out if you want that 21 MB back.

Here is the IPs he's used 150.129.8.8 162.247.74.216 176.10.99.200 185.220.100.245 185.220.101.140 185.220.101.141 185.220.101.202 23.129.64.192 51.255.77.78 77.247.181.163 77.247.181.165 91.250.242.12 Probably all proxies and VPNs, but it would be useful to get this criminal banned from his VPN subscription too. The VPN company can probably look at their logs and notify the local authorities of where he lives too.

This suspension shouldn't have come as much of a surprise because we provide a tool to monitor your own account load If you weren't aware of this Account Load tool it cane be found in cpanel at https://tommy.heliohost.org:2083/frontend/paper_lantern/load/index.live.php

It looks like your account never got unsuspended. Sorry about that. Thanks for bumping the thread.

You need to do your migrations and rakes and whatnot on your development system, and then upload the resulting files to Tommy. If that doesn't work and you need shell access you have to get a VPS. They start at $4 USD per month and you get root access to the whole server. https://www.heliohost.org/vps/

Unarchived.

Unarchived.

Unarchived.

Is there anything in the error log? Most modern browsers won't autofill your username and password into a site that doesn't have ssl. Is that what you mean?

You can also set up a python script in cgi to kill your own processes using a method similar to this https://wiki.helionet.org/tutorials/discord-bot#starting-and-stopping-your-bot

It looks like Flazepe changed it from 2.7 to 3.6 2019-10-26 for some reason. He probably thought it was a typo or outdated info or something http://wikiold.helionet.org/index.php?title=Django&oldid=691

Done. You should now be able to log in and your website should start working within 2 hours.

Fixed.

Ricky supports Django on Python 2.7. Would you like to be moved to Ricky?

I created a new file rortest_2.4.10.tar.gz that has this change, and updated the wiki page to have the new link https://wiki.helionet.org/tutorials/ror

Do you need a gem installed? EDIT: I edited your file /home/jciccio/ror/rortest/Gemfile and changed the line that said '2.4.9' and changed it to '2.4.10'. The system ror version was updated at some point. There you go https://jciccio.heliohost.org/rortest

Did you wait 2 hours after you installed the certificate for it to start working?