Closed Bug 1129008 Opened 10 years ago Closed 9 years ago

hello does not work stating firewall, firefox-specific

Categories

(Hello (Loop) :: Client, defect, P5)

x86_64
Windows 7
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cshields, Unassigned)

Details

(Whiteboard: [watch][error])

In Firefox 35.0.1, Windows 7 I tried using Hello today - every time I try it, it seems to connect but with a gray screen for a few seconds followed with "The stream was unable to connect due to a network error. Make sure your connection isn't blocked by a firewall." I tried on my laptop to rule out issues with my home router and the laptop (OSX) worked fine. I tried after disabling Windows firewall altogether, but no luck. I tried in Chrome on the same computer and it worked, so this seems to be specific to Firefox. Happy to help troubleshoot this or provide any further details, 'cshields' on irc.
Maire, this seems like it could be an ice issue or something... can one of the platform team work through it with Corey?
Flags: needinfo?(mreavy)
Corey -- Can you retest this and see if you're still having a problem? We were seeing server issues around this time that caused this type of error message, and that server issue has been resolved. If you're still seeing this problem with Release (Fx36), can you also test with Nightly (Fx39) and see if the behavior is any different? Thanks.
Flags: needinfo?(mreavy) → needinfo?(cshields)
I have the same issue (msg about firewall) but also a lot of other issues : 1-When I have not this issue , I'm very often disconnected after about 30 seconds 2-When I have the connction , the sound is quite poor (lot of noise) I'm working between 2PC altogether under XP and Firefox 36.0.1
Saintache -- Can you come to #loop on moznet (irc) when you get a chance? I think you may be having a combination of platform and front-end issues, and I think it will be easier/quicker to debug them in real-time. (If most of the issues are platform, I may ask you to move over to #media. I hang out in both irc channels.) Thanks!
Flags: needinfo?(saintache69)
(In reply to Saintache from comment #3) > I have the same issue (msg about firewall) but also a lot of other issues : > 1-When I have not this issue , I'm very often disconnected after about 30 > seconds > 2-When I have the connction , the sound is quite poor (lot of noise) > > I'm working between 2PC altogether under XP and Firefox 36.0.1 (In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #4) > Saintache -- Can you come to #loop on moznet (irc) when you get a chance? I > think you may be having a combination of platform and front-end issues, and > I think it will be easier/quicker to debug them in real-time. (If most of > the issues are platform, I may ask you to move over to #media. I hang out > in both irc channels.) Thanks! >Maire Reavy I'm not sure to fully understand your reply. I suppose that I must start by downloading moznet (on the 2 PCs ?) But what means #loop and #media . Perhaps it will be clearer after installing moznet ?
Flags: needinfo?(mreavy)
Hi Saintache, details about IRC are here: https://wiki.mozilla.org/IRC
Sorry for the confusing reply, Saintache. As Mark says in Comment 6, I would like you to come to mozilla's irc for a real-time chat with our developers to see if we can resolve your problems more quickly.
Flags: needinfo?(mreavy)
(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #2) > Corey -- Can you retest this and see if you're still having a problem? We > were seeing server issues around this time that caused this type of error > message, and that server issue has been resolved. > > If you're still seeing this problem with Release (Fx36), can you also test > with Nightly (Fx39) and see if the behavior is any different? Thanks. Sorry for the delay on this bug - today I tested with Fx38 and release (Fx36) and it works fine! Happy to write this bug off as the server issue, will let you close it out if you think Saintache has a different problem.
Flags: needinfo?(cshields)
Happened again today after a successful call yesterday. "The stream was unable to connect due to a network error. Make sure your connection isn't blocked by a firewall." Server issues again
(In reply to Corey Shields [:cshields] from comment #9) > "The stream was unable to connect due to a network error. Make sure your > connection isn't blocked by a firewall." Is it possible that one end of the call is a slow machine (with slow set-up times for video/audio)? > Server issues again I've not heard of any particular issues happening recently. Do you know if this was the same network setup at each end as your previously successful call? Did it reproduce a second time or was it consistent? Also, if you have this happen again, if you've generated the link (or your peer if they generated it), can you go to about:webrtc look for the "PeerConnection ID" line and send it to me via direct email? I can then take a look at the details of what went wrong and see if we can get some more information about it.
Flags: needinfo?(cshields)
(In reply to Mark Banner (:standard8) from comment #10) > I've not heard of any particular issues happening recently. > > Do you know if this was the same network setup at each end as your > previously successful call? It was not.. This was an attempt with someone from the UK, we had not had a successful call before this was a new attempt at hello for him. > Did it reproduce a second time or was it consistent? Yes, tried many times and did not connect. > Also, if you have this happen again, if you've generated the link (or your > peer if they generated it), can you go to about:webrtc look for the > "PeerConnection ID" line and send it to me via direct email? Will do thanks!
Flags: needinfo?(cshields)
need more data to fix (P5 until unblocked). adam is trying for more data on back end and also requested logs from user reported next time they see it.
Rank: 55
Flags: firefox-backlog+
Priority: -- → P5
Whiteboard: [watch][error]
No response from Saintache. Given that Corey isn't having the issue any more, I'm going to close this as WFM. We're also delving into stats at the moment and trying to find out if this is still happening frequently or not. If anyone hits this again, please file a new bug. Having a reference to a room that had the failure would be especially useful.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(saintache69)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.