Closed Bug 1647938 Opened 6 years ago Closed 6 years ago

Firefox Sync won't sync

Categories

(Firefox :: Sync, defect, P2)

77 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 1649856

People

(Reporter: soldier4messiah, Unassigned)

References

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

I logged into Firefox Sync. I clicked on the Sync button 10 times. When I looked to see if the Bookmarks were synced. They were not after each "sync". I have Firefox 77.0.1 64-bit and Windows 10 - 1909 installed.

Actual results:

No sync. My bookmarks did not sync.

Expected results:

All of my bookmarks should have synced to my computer.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → CSS Parsing and Computation
Product: Firefox → Core

(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #1)
Not quite a good guess :-)

Component: CSS Parsing and Computation → Sync
Product: Core → Firefox
Priority: -- → P2

The logs show a network issue connecting to the sync servers. Are you behind a VPN or proxy? Is it possible to try again on a different network?

Flags: needinfo?(soldier4messiah)

I am having this same issue, though with a different server. I've tried multiple computers and multiple networks, and I get 401 not authorized on all of them.

This is the URL that can't be accessed.

https://sync-733-us-west-2.sync.services.mozilla.com/1.5/121063734/info/collections

I deleted my account and created a new one. That got my sync profile assigned to a server that is working.

I deleted my account and created a new one. That got my sync profile assigned to a server that is working.

I'm glad to hear you got unstuck, and thanks for taking the time to report this and provide logs.

The first log shows the request to tokenserver failing with a timeout, but the sync still proceeds. I'm not sure what token it's using for the sync since the call to tokenserver failed! But I'm not surprised to see it get a 401 when it tries.

The second log seems to to sync using an already-obtained token, get a 401, then successfully refresh its token.

So...I'm not sure what to make of these logs yet, but the first one at least definitely seems to be Firefox doing something buggy.

Flags: needinfo?(soldier4messiah)

I expect this is due to the same underlying cause as Bug 1649856, but not ready to mark it as a dupe just yet.

See Also: → 1649856

(In reply to Ryan Kelly [:rfkelly] from comment #7)

The first log shows the request to tokenserver failing with a timeout, but the sync still proceeds. I'm not sure what token it's using for the sync since the call to tokenserver failed! But I'm not surprised to see it get a 401 when it tries.

According to this comment that's "expected" :/

According to this comment that's "expected" :/

Firefox Sync: Doing Weird Stuff On Purpose since 2007.

Thanks Mark, if that is indeed expected then I think we can dupe this to Bug 1649856.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: