I don't really think it's Node.js-related. Under what kind of network are you and who is managing your firewall? Does it block any other ports in the same way or only 13130?
There is no "best" port for any application. They will all run equally well on any port (of course first 1024 well-known ports are reserved for things like HTTP, SSL, FTP and you shouldn't use them). There are some common ports though. If you have a web server on port 80, it's common to have some other web service on 8080 (node.js app for example). I'd say run your node apps on ports which your network administrator can leave open. On Wednesday, 29 April 2015 00:14:11 UTC+2, reza zamani wrote: > > Hi > we're using node.js on linux server and we have configured it on port > 13130. > It works well for 2 or 3 days, but suddenly the port is blocked (i think > maybe by firewall) and the service gets down. > so we have to open the port again and reset node.js to have it worked > again. > First: Why does this happen to us? > Second : Which port is the best for node.js? > third: Is there any technique to use and configure Node.js that we don't > know? > > Thanks you for help > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/04cf5d51-1aef-4a3b-9ae3-aed888087051%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
