All Activity

ok for the port. I wish I picked a less obvious one then. I'm not sure what you mean by "set up passenger" as my understanding was that it was automatically installed when we were using node.js, it wasn't a conscious choice from my side. My goal was to use https://citadel.helioho.st/ as the main website (it's the only domain i have created). Right now i can access it, and the html works, but the consol says : network.js:3 WebSocket connection to 'wss://citadel.helioho.st/' failed: And it's not possible to play the game. However, I can acess https://wss.citadel.helioho.st/ and this one loads both the html and the websocket, allowing the game to be played. Is that expected behaviour ? If so, is there a way for me to redirect traffic from https://citadel.helioho.st/ to https://wss.citadel.helioho.st/, so I can use the more elegant website name as an entry point for visitors ?

Thank you

Since you set up Passenger on citadel.helioho.st I assumed you wanted to put a website on that domain, so I made another domain for the websocket. It doesn't really matter which port you use. If someone else comes along and tries to use port 8080 it will say it's already in use if your websocket is already running. If you stop your websocket and someone else starts using 8080 then you won't be able to start your websocket anymore.

Indeed it's now working on https://wss.citadel.helioho.st/ ! Thank you !! However https://citadel.helioho.st/ had a nicer ring to it 😄, i'm guessing it's not possible to use this domain instead, because of the websockets issue ? (swap https://citadel.helioho.st/ and https://wss.citadel.helioho.st/ ?) I'm down for trying to move the files myself, but don't want to break anything in the process, as I haven't understood completely how it got solved. Also, I've used the 8080 port randomly, since 3000 was taken. Is it smart to have used this one, and not a more obscure/random one ? Does it make a difference ? (since you said "There are 65535 internal ports, and only a handful are in use by other users") Thanks again

Ok, I created the proxy to port 8080 on wss://wss.citadel.helioho.st and it seems to be working root@control [~]# ./websocat wss://wss.citadel.helioho.st hello ^C And the logs show this

How do I mark this fixed 😢

Hi, My account associated with the email lubdhak98@gmail.com was suspended due to the Multiple Account Detection system. I would like to clarify that I only have one account and request a review of the suspension. Please let me know if any additional information is needed.

I have added heliosinfosystem.com to your account. The complete URL you asked for of heliosinfosystem.com/bid-e is a path and cannot be added to accounts. If you want the heliosinfosystem.com/bid-e path to redirect to your main domain, you could use an htaccess redirect. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

heliosinfosystem.com is my domain. I want to add heliosinfosystem.com/bid-e as a DNS entry so that this route diverts traffic to my website

Ok, https://control.citadel.helioho.st/ works now, and the server is running : server.js is running. Stop Current memory usage: 64.07 MB Estimated 24 hour usage: 90.10 GB - Check Load Logs: Clear Logs - Full Logs [2025-06-27 22:06:54] Starting server.js. SERVER STARTED AND RUNNING Server running on port 8080 [2025-06-28 08:26:41] Starting server.js. SERVER STARTED AND RUNNING Server running on port 8080 However, the websocketsin the game itself seem to be still be blocked : network.js:3 WebSocket connection to 'wss://citadel.helioho.st/' failed: setupWebSocket @ network.js:3 (anonymous) @ game.js:39 Is there something i should do in wss.citadel.helioho.st ?

Perfect thanks. It worked!

We traditionally don't whitelist certain IPs, so if you have a service connecting over FTP from an Azure server, as long as it uses the correct credentials, it shouldn't get blocked.

I did notice these domains are trying to send emails despite the limit being 0. Want me to set the nilijua.xyz limit to 50 or can you figure out where the 9 emails came from first?

The above is fine. Activate nilijua.xyz I test

Ok, give me a few hours I back up everything then we reset it. Don't worry, I won't re-upload the files. Just need them for reference as I recreate everything

Thanks a lot ! I have moved the files. I am going to bed now but will carry on first thing tomorrow

Ok, let's leave Passenger on for your main domain so you can play around with that. I created 2 subdomains for you: wss.citadel.helioho.st which we'll use for your websocket, and control.citadel.helioho.st that we'll use for your start/stop/logs index.sh script. The new domains should start working in about 100 minutes or so. You can go ahead and move the .htaccess file and index.sh file from /home/citadel.helioho.st/httpdocs/bot_control/ to /home/citadel.helioho.st/control.citadel.helioho.st/ We'll work on this more when the domains are ready.

I am unsure if there is something else I can do from my side ? You said : we need to either add another subdomain to access /bot_control/ or you'll need to disable Passenger. I am down for either, but as I mentioned, I am lost. Is there a tutorial I can follow for any one of these options ? I'll be glad to stop bothering you, I just don't know what i'm supposed to do next

No external ports are available, and we don't open them in the firewall on Morty, Tommy, or Johnny. Internal ports are basically all available, but they can't be accessed remotely without proxying them through Apache or Nginx because the firewall blocks the direct connection. There are 65535 internal ports, and only a handful are in use by other users. Right now Passenger is blocking access to everything on your domain, so we need to either add another subdomain to access /bot_control/ or you'll need to disable Passenger.

I thought the whole point was that no port was available ;( that's why i didn't try further I switched to 8080 and it works now indeed : server.js is running. Stop Current memory usage: 62.12 MB Estimated 24 hour usage: 87.36 GB - Check Load However on the main game itself : network.js:3 WebSocket connection to 'wss://citadel.helioho.st/' failed: setupWebSocket @ network.js:3 (anonymous) @ game.js:39 Is that where nginx/apache are needed ? I've been able to stop the script as well server.js is not running. Start - Check Load Logs: Clear Logs - Full Logs [2025-06-27 21:48:01] Stop action requested for server.js. [2025-06-27 21:48:38] Stop action requested for server.js. [2025-06-27 21:50:19] Stop action requested for server.js. [2025-06-27 21:52:03] Stopping server.js.

Switch to another port other than 3000. Obviously someone else is using 3000.

thank you, it seems to work ! now i'm blocked by the port issue we discussed, but i'm guessing that's expected ? Only need the apache/nginx redirect that was mentioned in the FAQ ? Or am i forgetting something [2025-06-27 19:35:41] Starting server.js. SERVER STARTED AND RUNNING node:events:496 throw er; // Unhandled 'error' event ^ Error: listen EADDRINUSE: address already in use :::3000 at Server.setupListenHandle [as _listen2] (node:net:1940:16) at listenInCluster (node:net:1997:12) at Server.listen (node:net:2102:7) at Object. (/home/citadel.helioho.st/server.js:548:8) at Module._compile (node:internal/modules/cjs/loader:1730:14) at Object..js (node:internal/modules/cjs/loader:1895:10) at Module.load (node:internal/modules/cjs/loader:1465:32) at Function._load (node:internal/modules/cjs/loader:1282:12) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) Emitted 'error' event on WebSocketServer instance at: at Server.emit (node:events:518:28) at emitErrorNT (node:net:1976:8) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '::', port: 3000 } Node.js v22.17.0

Instead of this Try this if [ "$QUERY_STRING" == "action=start" ]; then if [ $running -ne 0 ]; then echo "$bot_name is already running..." else echo "[$ts] Starting $bot_name." >> $pwd/$log_name /opt/plesk/node/22/bin/node /home/$main_domain/$bot_name >> $pwd/$log_name 2>&1 & echo "Starting $bot_name...<script>window.location.replace('/$control/');</script>" fi fi

I have not been able to start and stop the websocket from the /bot_control/index.sh script, it is looking for the node install folder and i don't know where to indicate it. it is looking in /usr/local/bin/node, but not finding it Could you please tell me what i need to change in that bash script to make it work with node.js ? In its initial state, it seemed to be looking for a python file only apologies for taking your time, i have been trying all day

Passenger automatically kills your Node.js server after 5-10 minutes without any page hits. That's why I was recommending starting and stopping your websocket with the /bot_control/index.sh script if you want it to run for more than 5 minutes.