Installing Signalmaster on production server

[Oluwafemikorede]

hello,

I installed signalmaster on my centos and I tried running node server.js and it shows server runs on localhost:8888, how do I change my config or settings to make server reflect my production url

[fippo]

the server should be listening on all interface by default -- https://github.com/andyet/signalmaster/blob/master/server.js#L29-L34 is slightly misleading about that.

Typically you will want to run this behind nginx or haproxy. See the socket.io documentation for this

[Oluwafemikorede]

@fippo will changing https://localhost: on https://github.com/andyet/signalmaster/blob/master/server.js#L29-L34 to my url resolve the issue?

And how can I "run this behind nginx or haproxy." my server runs on apache

[fippo]

there should be no issue, you can ignore console.log output

[xdumaine]

You don't need to change that, it's just a logged value. It's already listening on the interface. Provided your DNS is configured, your URL will work.

[Oluwafemikorede]

I followed the installation steps but I am not getting "Welcome to socket.io" when I point my browser to the url, any reason why this might be happening

[fippo]

the README is outdated :-( If you get a {"code":0,"message":"Transport unknown"}

from http://yourservernamehere:8888/socket.io/ you should be good

[Oluwafemikorede]

thanks, it works, so my signalling service will now be something like this right...

http://yourservernamehere:8888/

but how do I change it to https, running this command

./scripts/generare-ssl-certs.sh

throws this error

-bash: ./scripts/generare-ssl-certs.sh: No such file or directory

[Oluwafemikorede]

thnaks everyone, all problems fixed now, I think the documentation needs to be updated. I can close the issue now.

[canturker]

@Oluwafemikorede how can you solved issue? I have same problem and cant find solution