901925 - Cannot add gmail email account

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Stefan Plewako [:stef]]

When I'm trying to setup gmail email account via wifi or 3g I always get 'Unable to establish a secure connection with "{{server}}". There may be a problem with your network or the server.' (setup-error-bad-security) error.

Geeksphone keon, fxos ver 1.1, build id 20130805051222, git rev 45f6a73b09292e16717fb2…

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

You are probably trying to connect to a domain name that doesn't match up with the certificate held by the server.  Or you are the victim of a MITM attack.  See https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo for the specifics, but in general what I would want to know is the domain you are typing in and whether you're using automatic/manual config, etc.  (The logcat is somewhat useful in this case, but if it's a hassle, but not essential since you provided the error code.  Thanks!)

Comment 2

[Stefan Plewako [:stef]]

Domain: gmail.com, probably no mitm (on both 3g and my home wifi? only on this device?), automatic and manual setup…

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

okay, going to need the logcat from https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo because gmail.com should definitely work.

Comment 4

[Stefan Plewako [:stef]]

Attachment: logcat.txt

This time was different, automatic setup failed but manual succeeded.

Comment 5

[Stefan Plewako [:stef]]

(In reply to Stefan Plewako [:stef] from comment #4)

Obvious typo in automatic setup, will try again.

Comment 6

[Stefan Plewako [:stef]]

I can not reproduce this anymore. I don't know if it was typo in all five (at least) tries (with updates and restarts in between) or sth else but with today build all is fine (checked few times) - strange… closing this bug as worksforme.

Comment 7

[Andrew Sutherland [:asuth] (he/him)]

The fact that you got a security error means we experienced some type of security problem.  Typo-ing "gmail.con" is unlikely to result in that happening unless your internet provider was turning NXDOMAIN results into bogus search results pages and something weird happened.

Another possibility is that your device's clock was very off so the certificate showed up as expired.

Comment 8

[Stefan Plewako [:stef]]

(In reply to Andrew Sutherland (:asuth) from comment #7)
> Another possibility is that your device's clock was very off so the
> certificate showed up as expired.

Device clock set to 1980 was the real culprit - I don't always remember to set date correctly after flashing…

Comment 9

[Andrew Sutherland [:asuth] (he/him)]

(In reply to Stefan Plewako [:stef] from comment #8)
> Device clock set to 1980 was the real culprit - I don't always remember to
> set date correctly after flashing…

I've heard of this happening to other people a number of times.  I've filed bug 907435 on getting a proper error message to help users of the app address this problem more directly.