Avatar for Username

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊，或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

Hello not working with network error - testing in Pacific Islands

  • 1 回覆
  • 2 有這個問題
  • 15 次檢視
  • 最近回覆由 guigs

leemingd
leemingd
more options

A few of us in the Pacific Islands Internet Society have been trying out Firefox Hello. The experience reported is that on a local network (ie same provider in same country) it works fine but several of us report errors when trying to use it internationally. Most countries here are still reliant on satellite links. We all tried with our AV, Windows and any other firewalls turned off but still the same error:

"The stream was unable to connect due to a network error. Make sure your connection isn't blocked by a firewall"

Could this be latency or low bandwidth, or an ISP QoS issue?

For instance I am using only a 256/128 connection, in SOlomon Islands that is the most that is affordable (USD 450 per month). Is Hello only useable with high bandwidth? If so, it is not a Skype replacement.

A few of us in the Pacific Islands Internet Society have been trying out Firefox Hello. The experience reported is that on a local network (ie same provider in same country) it works fine but several of us report errors when trying to use it internationally. Most countries here are still reliant on satellite links. We all tried with our AV, Windows and any other firewalls turned off but still the same error: "The stream was unable to connect due to a network error. Make sure your connection isn't blocked by a firewall" Could this be latency or low bandwidth, or an ISP QoS issue? For instance I am using only a 256/128 connection, in SOlomon Islands that is the most that is affordable (USD 450 per month). Is Hello only useable with high bandwidth? If so, it is not a Skype replacement.

所有回覆 (1)

guigs
guigs
more options

Hi leemingd, In order to further investigate the network error it may be necessary to gather logs: 

   In order to investigate if something went wrong we will need to collect more information:
  1. Open up about:webrtc in the url, start a conversation with a new link.
  2. Click on "start debug mode" and "start AEC logging" try to connect in the url, wait for the error then click on connection log.
  3. Use pastebin.mozilla.org to share the logs.