X
Nhấn vào đây để đến phiên bản di động của trang web.

Diễn đàn trợ giúp

Since Firefox 36 Release Port 1935 traffic is blocked. Why?

Được đăng

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 webmaster@hos.com

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 webmaster@hos.com

Giải pháp được chọn

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:

Đọc câu trả lời này trong ngữ cảnh 0

Chi tiết hệ thống bổ sung

Phần bổ trợ đã cài đặt

  • Adobe PDF Plug-In For Firefox and Netscape 10.1.13
  • Google Update
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Next Generation Java Plug-in 11.25.2 for Mozilla browsers
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Shockwave Flash 17.0 r0
  • 5.1.31211.0
  • NPWLPG
  • iTunes Detector Plug-in

Ứng dụng

  • Chuỗi đại diện người dùng: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0

Thông tin chi tiết

guigs 1072 giải pháp 11697 câu trả lời
Được đăng

Giải pháp được chọn

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:

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. *[http://www-archive.mozilla.org/projects/netlib/PortBanning.html] There should not be a need for this, because the port you mentioned is not explicitly on the banned list see the [http://lxr.mozilla.org/mozilla-central/source/netwerk/base/nsIOService.cpp source] Overriding these ports listed is this about:config: *[http://kb.mozillazine.org/Network.security.ports.banned.override]

Người tạo câu hỏi

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 webmaster@hos.com

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

''HeartsOfSpace [[#question-1056668|said]]'' <blockquote> 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 webmaster@hos.com </blockquote> 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