Closed Bug 1453833 Opened 6 years ago Closed 6 years ago

Firefox Sync no longer syncing passwords / logins

Categories

(Firefox :: Sync, defect)

59 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: foss, Unassigned)

Details

Attachments

(4 files, 1 obsolete file)

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180327091359

Steps to reproduce:

Debug info:
* Operating system: Fedora 27
* Firefox version: 59.0.2

1. Open Firefox on existing device added to Firefox Sync
2. Go to site with saved password
3. Click on "username" box


Actual results:

No response from "username" box with prompt for saved email or username.

No passwords listed under Preferences > Privacy & Security > Saved Logins.

Also, a new session for my desktop appears under Devices in Firefox Sync. There are now two copies of the same device with the same name, except one was "last seen" a few days ago.


Expected results:

When clicking on a login box (e.g. email or username), I should be prompted for the login. Alternatively, typing the email or username should auto-fill the password in the password field. Neither work.
Bug 1453833 is almost certainly related. If you open the "Browser Console" or an error log from about:sync-logs, and see "Services.logins is undefined", then yeah, this bug is a dupe of that.
(In reply to Mark Hammond [:markh] from comment #1)
> Bug 1453833 is almost certainly related. If you open the "Browser Console"
> or an error log from about:sync-logs, and see "Services.logins is
> undefined", then yeah, this bug is a dupe of that.

I don't see this error in my Browser Console. Is there a log file I can check to be sure?
If you visit about:sync-logs and see any errors logs there, can you please attach the most recent to this bug?
about:sync-logs is in invalid URL for me. Are there debug options I need to enable for this page to become visible?
Sorry, my mistake, it is about:sync-log - no trailing "s"
I grepped through all of the log files present for 'Services.login' and nothing came up. I grepped for 'login' and I'm uploading some of the output spanning multiple log files. I also am attaching two full logs, since the day I noticed my initial disconnect had a long long. I'm also uploading the most recent log I have from yesterday.
Attachment #8967584 - Attachment is obsolete: true
The error from those logs is security related - SEC_ERROR_OCSP_SERVER_ERROR - do you have antivirus software installed? If so, could you see if the problem goes away when it is disabled or completely removed?
I should also note that the errors shown here may just be transient network errors, but would affect syncing of *all* data, not just logins. If it appears Sync is generally working other than passwords/logins, then please upload all error files shown in about:sync-log, as the actual error of interest may be in a different one.
Component: Untriaged → Sync
(In reply to Mark Hammond [:markh] from comment #9)
> The error from those logs is security related - SEC_ERROR_OCSP_SERVER_ERROR
> - do you have antivirus software installed? If so, could you see if the
> problem goes away when it is disabled or completely removed?

I'm on Linux 4.15.15 (Fedora 27), so the closest guess I could make is SELinux. I tried `setenforce 0` and restarted Firefox to see if there would be a difference, but my logins were still not syncing.

(In reply to Mark Hammond [:markh] from comment #10)
> I should also note that the errors shown here may just be transient network
> errors, but would affect syncing of *all* data, not just logins. If it
> appears Sync is generally working other than passwords/logins, then please
> upload all error files shown in about:sync-log, as the actual error of
> interest may be in a different one.

This morning, when I started up my desktop, I was signed out of Firefox Sync again, and a new log was created. I grabbed that one before changing devices, and I will upload it after this comment. If that log is not helpful, I will upload them all later in the day.
That log certainly implies something weird is going on specifically with your login storage - but not what that might be. The best I can suggest is:

* Disconnect Firefox from Sync and manually rm the old log files.
* Follow the instructions at https://wiki.mozilla.org/CloudServices/Sync/File_a_desktop_bug and enable "success" logging.
* Also follow the instructions at https://wiki.mozilla.org/Firefox:Password_Manager_Debugging to debug the password manager.
* Re-login to sync using your existing password, Sync.
* Check browser console for password manager errors.
* Restart, re-sync.
* Re-check browser console for more errors.
* Attach a zip of all log files in about:sync-log, and anything interesting from the browser console.

Sorry for this being such a PITA, and thanks for your patience and help!
I followed these steps; however, immediately after disconnecting and reconnecting from Sync, all of my login credentials were synchronized again. I now have access to my passwords again.

After I disconnected and reconnected to Sync, I noticed a lot of output in the browser console. It appeared that Sync re-downloaded all of my saved logins (I saw all of the services I have saved credentials for pass by in the console, and then Sync confirmed they were found and added).

I followed all of the other steps regardless and it did produce a few error logs. However, they seemed to contain a significant amount of my browser history and I would prefer to not share the logs. I grepped for 'ERROR' in both log files, but only had this output:

> 1523893782306	Sync.SyncScheduler	ERROR	Engine bookmarks found 1 new records that failed to apply
> 1523894083212	Sync.ErrorHandler	ERROR	Some engines did not sync correctly.

I should have grabbed a few lines from browser console when I noticed Sync found the passwords, but I restarted the browser and lost it in scrollback.

As of now, this is fixed for me, and the "fix" was just disconnecting and reconnecting to Sync; we can keep it open for maybe another week if you'd like, in case it comes up again, but otherwise, my issue is resolved now.
Thanks for getting back to us.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: