1061583 - [Loop] Impossible to reach the msisdn server

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Gaia::Loop, defect)

Description

[mbarone]

Attachment: tcpdump_MobileID.txt

Device: Flame
Build Id:20140827020173649
Gecko-8c904cf Gaia-d72f8ad
Platform Version: 32

STR
Suddenly the device is not able to connect to the server. Yesterday I was working with Loop app performing calls, but today I can't log into the app. Same Loop app and same build.

CASE 1 - Clicking on 'Use Phone number' button, but nothing happens. Logcat attached (Log1.txt).

CASE 2 - Click on 'Use Fx Account' button. Introduce valid FxA credential (email) and then click on OK. In this case the the Age verification window is shown instead of the password verification window. Same problem if I try to log with FxA from Settings. 

01-14 04:39:07.059 I/Gecko   (  296): 1136347071	Hawk	DEBUG	(Response) /account/login: code: null - Status text: null
01-14 04:39:07.059 I/Gecko   (  296): 1136347071	Hawk	DEBUG	Response text:
01-14 04:39:07.079 I/Gecko   (  296): 1136347091	FirefoxAccounts	ERROR	error POSTing /account/login: {"error":{},"message":null,"code":null,"errno":null}
01-14 04:39:07.079 I/Gecko   (  296): 1136347093	FirefoxAccounts	ERROR	SERVER_ERROR

In both cases we see that the device doesn't reach the server (wifi and 3g). Attached also tcpdump (I'm not sure this file helps because the traffic is https)

I've used the browser to check the connectivity and the internet connection works fine. I was able to visit some webpages.

Then we tried to open the page https://api.accounts.firefox.com/ in the browser without any success.

Then we tried to open the page https://msisdn.services.mozilla.com in the browser. In this case with success.

At this point the user can use the mobile ID flow (but there is another error). The flow is blocked on connecting... (Log2.txt).

Comment 1

[mbarone]

Attachment: Log1.txt

Comment 2

[mbarone]

Attachment: Log2.txt

Comment 3

[mbarone]

Let me know if you need more dumps.

Comment 4

[Alexis Metaireau (:alexis)]

It's possible that the FxA servers went down, since they are a dependency in both cases where you've seen a failure.

Chris, can you tell if something happened on the fxA server?

Comment 5

[mbarone]

The FxA server is up, because we can use Loop with other devices (Flame and Fire E)

Comment 6

[Alexis Metaireau (:alexis)]

Then I don't understand your statement:

> Then we tried to open the page https://api.accounts.firefox.com/ in the browser without any success.

That's the same URL we're using, so if that was down, that could be the root of the problem.

Comment 7

[Chris Karlof [:ckarlof]]

I'm not aware of any FxA outages.

:mbarone, what was the error you received when you fetched https://api.accounts.firefox.com?

Do you still have a problem? It is reachable by me.

We deployed a new version last week, which triggers a DNS switchover. Could this possibly a DNS caching issue on the client?

Comment 8

[Martijn Wargers (dead)]

Is this still a problem? With the UI test app - Privileged, I'm able to access the msisdn server just fine.

Comment 9

[Rémy Hubscher (:natim)]

Let's close it and we can file a new bug in case it happen again.
We are also adding some log to the loop-server in Bug 1064971 to make sure we have enough information to be able to debug this kind of errors in the future.

Comment 10

[James Bonacci [:jbonacci]]

OK.