Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Can't sign in to sync

  • 2 replies
  • 8 have this problem
  • 207 views
  • Last reply by antiqueornot
  • Solved

antiqueornot
antiqueornot

Am running the latest version of Firefox (32.0.2) on three devices: a PC laptop, a Macbook, and an iMac. On each and every machine, cannot sign in to Firefox Sync. Every time I receive a "connection interrupted" error. Yesterday I set up two Firefox Sync accounts (one for me and one for my husband), but today I can't use either of them because we can't sign in. What can we do?

Am running the latest version of Firefox (32.0.2) on three devices: a PC laptop, a Macbook, and an iMac. On each and every machine, cannot sign in to Firefox Sync. Every time I receive a "connection interrupted" error. Yesterday I set up two Firefox Sync accounts (one for me and one for my husband), but today I can't use either of them because we can't sign in. What can we do?

Chosen solution

Apparently the problem has solved itself. When I tried to recreate the error message screen, I was able to log in. Guess Firefox had a glitch that's been resolved.

Thanks so much for trying to help, guigs2.

Read this answer in context 👍 1

All Replies (2)

guigs
guigs

HI antiqueornot, I understand when you try to connect to Firefox Sync that there are connection errors. Can you please attach a screenshot of the error How do I create a screenshot of my problem?

Also, are you using the new version of sync, where you can login at accounts.firefox.com?

antiqueornot
antiqueornot Question owner

Chosen Solution

Apparently the problem has solved itself. When I tried to recreate the error message screen, I was able to log in. Guess Firefox had a glitch that's been resolved.

Thanks so much for trying to help, guigs2.