Since Firefox 36 Release Port 1935 traffic is blocked. Why?
Our streaming audio service has been using Adobe Flash Player since 2007. With the February 2015 release of Firefox 36 many of our customers (Windows and Mac) are seeing our Flash player hang indefinitely at "Trying connection on port 1935". In somecases reinstalling Adobe Flash Player will fix this; in other cases reinstalling Firefox will fix this; in several cases only allowing incoming connections on port 1935 (new firewall rule) will fix this.
What happened? A lot of our customers use Firefox and suddenly no joy.
Thank you!
Joseph Jacobs Webmaster Hearts of Space Inc [email protected]
選ばれた解決策
Currently I cannot find the source of the change to this port, however to tell if it is Firefox the error will mention Firefox has blocked it specifically. In the past you could use user.js file to block and unblock ports in firefox as well.
There should not be a need for this, because the port you mentioned is not explicitly on the banned list see the source
Overriding these ports listed is this about:config:
この回答をすべて読む 👍 0すべての返信 (2)
選ばれた解決策
Currently I cannot find the source of the change to this port, however to tell if it is Firefox the error will mention Firefox has blocked it specifically. In the past you could use user.js file to block and unblock ports in firefox as well.
There should not be a need for this, because the port you mentioned is not explicitly on the banned list see the source
Overriding these ports listed is this about:config:
HeartsOfSpace said
Our streaming audio service has been using Adobe Flash Player since 2007. With the February 2015 release of Firefox 36 many of our customers (Windows and Mac) are seeing our Flash player hang indefinitely at "Trying connection on port 1935". In somecases reinstalling Adobe Flash Player will fix this; in other cases reinstalling Firefox will fix this; in several cases only allowing incoming connections on port 1935 (new firewall rule) will fix this. What happened? A lot of our customers use Firefox and suddenly no joy. Thank you! Joseph Jacobs Webmaster Hearts of Space Inc [email protected]
OK, this turned out to be a problem with the new, more strict security rules implemented in Firefox 36> and newer: TLS is implemented now. One of our streaming servers had an outdated SSL bundle causing the Adobe Flash Player in Firefox to hang. The problem has nothing to do with port 1935. The problems is that Firefox cannot display an alert identifying the problem, yet FF is preventing the Flash player from connecting to the streaming server because it wants to see the valid SSL bundle.
Cheers,
HoS