Page 1 of 1

Configure on port 60 instead?

Posted: 20 Sep 2024, 01:57
by dorishuntt
I can't seem to get BlueBox to work. And the examples does not connect, either. The page at localhost:6060/BlueBox does not display either and the firewall was disabled at the time.
I run CentOS5 - and have configured the server at 81.7.144.112, port 9339 as usual + followed the instructions meticously and restarted the system/services.
The server is a normal Dell rackserver.
I have no problems, connecting as usual - but routered computers still cannot.

However, could a solution be to disable the Apache - and then configure smartFoxServer to use port 60, which is open on most computers? Can it be done, somehow?

Re: Configure on port 60 instead?

Posted: 20 Sep 2024, 06:34
by Lapo
Hi,
The page at localhost:6060/BlueBox

the default for BlueBox is 8080, not 6060. Did you change it?

If so you should be able to point your browser at http://<your-address>:6060 and see a welcome page. If that doesn't work check the server side logs for errors.

However, could a solution be to disable the Apache - and then configure smartFoxServer to use port 60, which is open on most computers? Can it be done, somehow?

Yes if Apache is not being used, shutting it down is a good idea as it will use resources (ports, RAM) for no reason.

As regards port 60, I don't think it's a good idea. The whole point of the BlueBox is to help clients that are behind restricted networks to be able to connect and play. By using a non default HTTP port it drastically reduces the chance that said players will be able to connect.

Ideal port values for BlueBox are 8080 or 80.
Just keep in mind that values below 1024 require the server (SFS2X) to run with root privileges.

Cheers