Closed (fixed)
Project:
Node.js integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Feb 2013 at 09:33 UTC
Updated:
2 Mar 2013 at 09:20 UTC
Jump to comment: Most recent
Comments
Comment #1
julien commentedI will try this by replacing xyz by your nodejs server port to open the port on your firewall
Comment #2
jurgenhaasAlready wanted to reply that I had exactly done that and while copying a line of code from the config file I realized that the port was 444 instead of 443 which has some other unrelated reason. Now I included that in the firewall config and of course it works just fine.
However, one more question regarding ports for the sockets. I guess that's working via UDP and I wonder what's your advise on which ports to open in and out for UDP.
Thanks for your quick help, this is really appreciated.
Comment #3
julien commentedCan you explain more on why you're guessing it is UDP ?
Comment #4
jurgenhaasThought the socket.io was using UDP, isn't it?
Comment #5
Anonymous (not verified) commentedlsof -i -n
will tell what is listening on what.
if you know the socket.io port, do:
lsof -i:$socket_io_port -n
should help you figure out which itpables rules you need.
Comment #6
jurgenhaasOK, got it. Thanks a lot for your help.