Sync not working due to a downed server
For now one week, I cannot sync my browser using Firefox sync. When checking the logs, I always see :
Sync.Resource WARN GET request to https://sync-788-us-west-2.sync.services.mozilla.com/1.5/208380794/info/collections failed: [Exception... "The connection was refused" nsresult: "0x804b000d (NS_ERROR_CONNECTION_REFUSED)" location: "<unknown>" data: no] No traceback available
I have tested on multiples wifi network and mobile data and still the same error. After checking, it seem that this server is down, and I don't know were to report this.
Is this the right place to report this or is it a thing I can do to fix that ?
Thanks
所有回复 (11)
Interesting.... What do you have set in the proxy settings? Try downloading Firefox from Mozilla. Download, unzip, and run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
Also, give Waterfox a try.
I have no issues. see screenshot
I have no proxy set but issue doesn't seems to be on my side, doing a traceroute, the network packets leave my network correctly.
Try and sync Firefox from Mozilla and see if you have the same issue.
Same issue
WOW... How about booting to a live usb stick, once on the desktop, log into your account and see if Firefox on the live stick syncs. What is your network setup? I have a router and then modem.
Still the same and as I say the problem is not related to my computer as the packet can leave my network without problem
I'm curious to know why you keep getting that same 1 server.
I don't think there is a dynamic server switching system
Dis this suddenly happen or are you using a profile that hasn't been used for quite some time?
cor-el said
Dis this suddenly happen or are you using a profile that hasn't been used for quite some time?
I was a account created on 15/09/2023 but it was only used on one computer, this is when I have recently setup a new computer that I have remarked the issue.
For more detail, see https://bugzilla.mozilla.org/show_bug.cgi?id=1879022
The feedback from the bug will be interesting.