[Krydos] Websockets ports

[gofterdom]

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 ?

[Krydos]

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

[gofterdom]

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

[Krydos]

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.

[gofterdom]

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 ?

 

 

[gofterdom]

Ok i managed to redirect from citadel to wss.citadel using .htaccess. If it's not possible to do otherwise, i guess it will be a good enough workaround for now. Thank you very much for all your help