If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

unable to start a call using Hello on nightly fx40 when using staging server

RESOLVED INCOMPLETE

Status

Hello (Loop)
Client
P4
normal
Rank:
45
RESOLVED INCOMPLETE
3 years ago
2 years ago

People

(Reporter: juanb, Unassigned)

Tracking

unspecified
x86
Mac OS X
Points:
---
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [watch][investigation])

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Using latest nightly 40.0 with a new profile, when I try to use Hello after changing the loop.server preference to use a staging server, the "Start Conversation" blue button doesn't work, and I cannot start a call.

Steps:
1. Launch the latest nightly with a new profile.
2. Go to about:config and change the loop.server preference to 
https://loop.stage.mozaws.net/v0
3. Restart the browser
4. Click on the Hello icon
5. Click on the "Start a conversation" blue button.

Expected: I can start a conversation

Actual: Nothing happens. Notice how the blue button "Start a conversation" is sort of grayed out.

This only happens if you change to the staging server. This used to work before, but I haven't tried finding a regression range.

This also seems to happen on release, and beta builds (I didn't try dev edition).
This works for me. Can you try

* Set the loop.debug.loglevel to "All"
* Restart FF
* Open the Browser Console straight away
* See if any errors/messages are on the console before or when you open the Hello panel.
Flags: needinfo?(jbecerra)
(Reporter)

Comment 2

3 years ago
(In reply to Mark Banner (:standard8) from comment #1)
> This works for me. Can you try
> 
> * Set the loop.debug.loglevel to "All"
> * Restart FF
> * Open the Browser Console straight away
> * See if any errors/messages are on the console before or when you open the
> Hello panel.

This is what appears in the browser console:

The Components object is deprecated. It will soon be removed. utils.js:9:0
"hawkRequest: /rooms" 1 MozLoopService.jsm:644
"PushHandler: initialize options = " Object {  } MozLoopPushHandler.jsm:387
"createNotificationChannel" "19d3f799-a8f3-4328-9822-b7cd02765832" 1 "rooms" MozLoopService.jsm:358
"PushHandler: channel registration: " "19d3f799-a8f3-4328-9822-b7cd02765832" MozLoopPushHandler.jsm:488
"assigning to deferredRegistrations for sessionType:" 1 MozLoopService.jsm:413
"PushHandler: attempt to open websocket to PushServer: " "wss://loop-push2.stage.mozaws.net/" MozLoopPushHandler.jsm:769
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] network-monitor.js:82:0
"PushHandler: websocket closed: delay and retry - " 2152398861 MozLoopPushHandler.jsm:576
"PushHandler: retry delay set for " 60000 MozLoopPushHandler.jsm:251
TypeError: document.getItems is not a function PageMetadata.jsm:125:39
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] update.xml
"PushHandler: attempt to open websocket to PushServer: " "wss://loop-push2.stage.mozaws.net/" MozLoopPushHandler.jsm:769
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] network-monitor.js:82:0
"PushHandler: websocket closed: delay and retry - " 2152398861 MozLoopPushHandler.jsm:576
"PushHandler: retry delay set for " 120000 MozLoopPushHandler.jsm:251
Flags: needinfo?(jbecerra)
Thanks Juan. Based on the log here and looking at bug 1154897, I think what is happening is that one of your add-ons is disabling access to websockets or something to do with websockets.

Could you try disabling them, and identifying the one at issue please?
Flags: needinfo?(jbecerra)
Whiteboard: dupeme
(Reporter)

Comment 4

3 years ago
Created attachment 8594050 [details]
websockets prefereces in about:config

All add-ons were disabled during testing. I am including a screenshot of the preferences in about:config for websockets. Is there anything suspicious there?
Flags: needinfo?(jbecerra)
Ok, I'm puzzled, would you be able to do a vidyo call maybe today or tomorrow to try out a few things and see if we can narrow down what's going on here? I can be found in the #loop channel on irc.
Flags: needinfo?(jbecerra)

Updated

3 years ago
Rank: 45
Flags: firefox-backlog+
Priority: -- → P4
Whiteboard: [watch][investigation]
I had a phone discussion with Juan a week or so ago about this, and we weren't able to reproduce at the time.

I don't think there's anything here we can act on, so I'm going to resolve this as incomplete for now; if we continue to have problems we can always reopen or file a new bug.

If we do see more problems, turning on the various loop debugging prefs would be useful.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(jbecerra)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.