Firewall (kaspersky/avast) blocked messages when I using websocket server (socket.io on node.js), what can i do? (except change default setting in firewall) port 8080 or 8000 thx a lot

link|improve this question
Do you mean it is blocking incoming connections to port 8080 and 8000? – kanaka Mar 14 '11 at 23:17
1. with avast don't working websockets and flashsockets protocol, 2 KIS blocking outcoming messages even by AJAX multipart streaming – Bart Mar 15 '11 at 6:41
sorry I didn't understand your comment. Can you clarify your setup? Which system is running the browser, which system is running socket.io/node.js, and where the "firewall" is running? Also, please try temporarily disabling your firewall software (make sure you are behind a router with basic firewalling first) and see if that gets things working. Then post you config and results of that test. – kanaka Mar 15 '11 at 14:34
feedback

migrated from stackoverflow.com May 11 at 3:49

This question came from our site for professional and enthusiast programmers.

3 Answers

up vote 1 down vote accepted

I can tell you 100% that Avast for example blocks not only websockets, but from what I see from my Socket.IO app also xhr-polling and other stuff.

This is unacceptable, I've even tested on port 80 and it doesn't work. What an awful piece of software.

Edit: this is a list of blocked ports by antiviruses

link|improve this answer
feedback

Many ISP companies block the port 80 to prevent their customers of hosting a web servers on their home computers.

It might beyond your power to unblock the port 80 from your ISP.

Also, as far as I am concerned, Avast is not a firewall.

link|improve this answer
feedback

You can try to use port 443 (which is used for https) if it's possible in your case.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown