Krydos

Your account was archived, not suspended. Suspended means you violated our terms of service or caused too much load. Archived means you haven't logged in to your account for a long time. To prevent your account from becoming archived again please remember to log in to cpanel at https://www.heliohost.org/login/ least once every 30 days. Unarchived.

Unblocked.

Donation verified, and max storage increased to 2000 MB.

Here's your error: # /home/lookyweb/node/test.js:5 user.cloudSession(419697811, function (err, cloud) { ^ TypeError: Cannot read property 'cloudSession' of undefined at /home/lookyweb/node/test.js:5:10 at /home/lookyweb/node/node_modules/scratch-api/scratchapi.js:105:7 at IncomingMessage.<anonymous> (/home/lookyweb/node/node_modules/scratch-api/scratchapi.js:39:37) at IncomingMessage.emit (events.js:203:15) at endReadableNT (_stream_readable.js:1145:12) at process._tickCallback (internal/process/next_tick.js:63:19) Passenger is what you would be using if you followed this guide https://wiki.helionet.org/tutorials/node.js

Yes, you can host those configurations on a VPS. https://www.heliohost.org/vps/

Remote access enabled.

It's fine to keep both your Tommy account and the VPS at the same time. To transfer your Tommy sites to the VPS I would use a temporary domain like hippo2.heliohost.org. You will need to install a webserver on the VPS for sure. Also I'm sure you probably use php and mysql so you'll need to install those too and anything else you'll need. I recommend using apache for your webserver on the VPS because that is what Tommy uses, and if you switch to nginx it may take some changes to get your site to work. Using apache you should be able to just copy your files over and it'll just work. Then when everything is functional on your temporary VPS domain, you can switch your main domain over to the new server with no downtime. If you need help with any of the above just ask. I'll start setting up your VPS now.

It was enabled on Tommy v1, but I never set it up again on Tommy v2 after I rebuilt him because no one has ever requested it. I would be willing to set it up again on Tommy, but not Ricky.

Are you starting/stopping it with python again, or is it running through passenger? If the latter what is the URL to it?

What is the url to the test python script?

Any error messages?

Pip automatically installs all dependencies. If dnspython wasn't installed it isn't a dependency. There you go https://krydos.heliohost.org/cgi-bin/modules37.py

Unarchived.

I would try mod_wstunnel.

What I would do is install apache or nginx to handle the ssl and certificates, and then proxy the socket through the web server. Either that or just run the socket without encryption.

See if any of this helps https://www.thesslstore.com/blog/ssl_error_rx_record_too_long/

Try accessing the https/wss by domain name instead of by ip.

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

Anything is better than wordpess. Thank you for getting rid of it.

Is FireFox accepting that certificate?

Unarchived.

Your wordpress install was hacked and used for illegal activity, and cannot be unsuspended or backed up. We strongly recommend not using wordpress for this and many other reasons. Literally any other software you could install on your account is better. I have removed your domain and your email address from the hacked account and sent a Johnny invite to your email address. Let us know if you have any problem creating a new account, and please don't install wordpress again because this will probably just happen again if you do.

You're on Tommy now. Thanks for the donation.

What kind of ssl certificate are you using for https/wss?

You can find limited logs at https://tommy.heliohost.org:2083/frontend/paper_lantern/stats/errlog.html in cpanel. Usually an admin can get a little better logs for you though. The reason users can't access the detailed logs directly themselves is because it's a shared server and there could be private information regarding the thousands of other accounts on your server. If you need direct access to full logs you'll need to get a VPS where you'll be the only user on the whole server, and you'll have root command line access to all of the logs.