Check if this answer works for you => /questions/1301042.

Doesn't help. I read about it. it looks like that is a solution (5 times click on the logo) for mobile devices running android. I talk about PC Version. So I head to the 3-bars-menu (upper right corner), click on Help, click on "About Firefox" and then the logo screen appears. If I click there on the logo or the name - nothing happens.

Firefox is installed here (my home) on two computers. Laptop and PC. On PC I still had version 79. Everything worked fine. But after updating - the trouble started. Same on the laptop yesterday after updating from 79 to 80.

BTW: I read something about docker solution? Someone here tried it on a Rasperry Pi/Docker Combo? And if yo - is there a manual how to setup ? (For german readers I used this manual for setup: https://jankarres.de/2014/07/raspberry-pi-firefox-sync-server-installieren/#comment-8641

That was "helter skelter" enough.

I don't understand why mozilla is not offering an easy solution. It took me hours and some days until averthing worked fine. And i do not really want to do all this again. I have a clue about computing but I am not a Crack. So it was very hard to me to set it up all. (And my english isn't the best).

It seems mozilla is not able to make things easy :( I tried to make a dowgrade back to 79. But a warning message pops up that i need to create a new profile. Thanks a lot!

After adding an -p -allow-downgrade to the command line i was able to start a firefox 79 again. And I can sync again. So it seems really there is a problem with v80.

And there is no easy way to block updates like a checkbox "no autoimatic updates". No. You need to hack the regestry or need to write a policy file :(

Workaround: "Ask before install update" is working now. But I guess it will not work very long.

Mozilla is really not able to make things easy :(

No "Backup" fuction to roll back. No "I really do not want updates" button. No simple server program for PC/Desktop version. "Why easy when you can things make hard", hu?

Same Problem here. We also use a personal Sync-Server. This one is installed on a Ubuntu VM. It works perfectly on Firefox ESR and Firefox 79 (rechecked with a downgrade). It absolutely does not work on Firefox 80 and 80.0.1.

Firefox always telling me to reconnect to Firefox Account.

Here is my log (changed domain to xyz.example.com for privacy)

1599203776387 Sync.Service INFO Starting sync at 2020-09-04 09:16:16 in browser session EYtMBSdodlF0 1599203776387 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1599203776391 Sync.Status INFO Resetting Status. 1599203776391 Sync.Status DEBUG Status.service: error.sync.failed => success.status_ok 1599203776392 FirefoxAccounts DEBUG FxAccountsProfileClient: Requested profile 1599203776392 FirefoxAccounts DEBUG getOAuthToken enter 1599203776393 FirefoxAccounts TRACE getCachedToken returning cached token 1599203776393 FirefoxAccounts DEBUG getOAuthToken returning a cached token 1599203776394 Sync.BrowserIDManager INFO Getting keys 1599203776394 Services.Common.RESTRequest DEBUG GET request to https://profile.accounts.firefox.com/v1/profile 1599203776395 Sync.BrowserIDManager INFO Getting an assertion from: https://xyz.example.com:16666/token/1.0/sync/1.5 1599203776395 Sync.BrowserIDManager DEBUG Getting a token using OAuth 1599203776395 FirefoxAccounts DEBUG getAccessToken enter 1599203776395 FirefoxAccounts DEBUG getOAuthToken enter 1599203776400 Services.Common.RESTRequest DEBUG POST request to https://api.accounts.firefox.com/v1/oauth/token 1599203776400 Services.Common.RESTRequest DEBUG POST Length: 127 1599203777063 Services.Common.RESTRequest DEBUG GET https://profile.accounts.firefox.com/v1/profile 304 1599203777077 Services.Common.RESTRequest DEBUG POST https://api.accounts.firefox.com/v1/oauth/token 200 1599203777077 Hawk DEBUG (Response) /oauth/token: code: 200 - Status text: OK 1599203777078 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -1077 1599203777078 FirefoxAccounts DEBUG _updateAccountData with items: ["oauthTokens"] 1599203777078 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203777079 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203777080 FirefoxAccounts DEBUG Using cached scopedKeys data for https://identity.mozilla.com/apps/oldsync 1599203777080 Services.Common.TokenServerClient DEBUG Beginning OAuth token exchange: https://xyz.example.com:16666/token/1.0/sync/1.5 1599203777081 Services.Common.RESTRequest DEBUG GET request to https://xyz.example.com:16666/token/1.0/sync/1.5 1599203777088 FirefoxAccounts TRACE finished write of json user data - took: 9 1599203777089 FirefoxAccounts DEBUG writing secure storage: ["kSync","kXCS","kExtSync","kExtKbHash","scopedKeys"] 1599203777089 FirefoxAccounts TRACE starting write of user data to the login manager 1599203777102 FirefoxAccounts TRACE finished write of user data to the login manager 1599203778241 Services.Common.RESTRequest DEBUG GET https://xyz.example.com:16666/token/1.0/sync/1.5 401 1599203778241 Services.Common.TokenServerClient DEBUG Got token response: 401 1599203778242 Services.Common.TokenServerClient INFO Server-reported error: {"location":"body","name":"","description":"Unauthorized"} 1599203778242 Services.Common.RESTRequest DEBUG POST request to https://api.accounts.firefox.com/v1/oauth/destroy 1599203778242 Services.Common.RESTRequest DEBUG POST Length: 969 1599203778242 FirefoxAccounts DEBUG _updateAccountData with items: ["oauthTokens"] 1599203778243 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778243 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778243 Sync.BrowserIDManager WARN Token server returned 401, refreshing certificate and retrying token fetch 1599203778243 FirefoxAccounts DEBUG _updateAccountData with items: ["cert"] 1599203778243 Sync.BrowserIDManager INFO Getting an assertion from: https://xyz.example.com:16666/token/1.0/sync/1.5 1599203778243 Sync.BrowserIDManager DEBUG Getting a token using OAuth 1599203778244 FirefoxAccounts DEBUG getAccessToken enter 1599203778244 FirefoxAccounts DEBUG getOAuthToken enter 1599203778250 FirefoxAccounts TRACE finished write of json user data - took: 7 1599203778250 FirefoxAccounts DEBUG writing secure storage: ["kSync","kXCS","kExtSync","kExtKbHash","scopedKeys"] 1599203778250 FirefoxAccounts TRACE starting write of user data to the login manager 1599203778256 FirefoxAccounts TRACE finished write of user data to the login manager 1599203778256 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778256 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778257 Services.Common.RESTRequest DEBUG POST request to https://api.accounts.firefox.com/v1/oauth/token 1599203778257 Services.Common.RESTRequest DEBUG POST Length: 127 1599203778262 FirefoxAccounts TRACE finished write of json user data - took: 6 1599203778262 FirefoxAccounts DEBUG writing secure storage: ["kSync","kXCS","kExtSync","kExtKbHash","scopedKeys"] 1599203778262 FirefoxAccounts TRACE starting write of user data to the login manager 1599203778268 FirefoxAccounts TRACE finished write of user data to the login manager 1599203778447 Services.Common.RESTRequest DEBUG POST https://api.accounts.firefox.com/v1/oauth/destroy 200 1599203778447 Hawk DEBUG (Response) /oauth/destroy: code: 200 - Status text: OK 1599203778447 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -1447 1599203778661 Services.Common.RESTRequest DEBUG POST https://api.accounts.firefox.com/v1/oauth/token 200 1599203778661 Hawk DEBUG (Response) /oauth/token: code: 200 - Status text: OK 1599203778661 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -1661 1599203778662 FirefoxAccounts DEBUG _updateAccountData with items: ["oauthTokens"] 1599203778662 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778662 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778662 FirefoxAccounts DEBUG Using cached scopedKeys data for https://identity.mozilla.com/apps/oldsync 1599203778662 Services.Common.TokenServerClient DEBUG Beginning OAuth token exchange: https://xyz.example.com:16666/token/1.0/sync/1.5 1599203778662 Services.Common.RESTRequest DEBUG GET request to https://xyz.example.com:16666/token/1.0/sync/1.5 1599203778669 FirefoxAccounts TRACE finished write of json user data - took: 7 1599203778669 FirefoxAccounts DEBUG writing secure storage: ["kSync","kXCS","kExtSync","kExtKbHash","scopedKeys"] 1599203778669 FirefoxAccounts TRACE starting write of user data to the login manager 1599203778676 FirefoxAccounts TRACE finished write of user data to the login manager 1599203778897 Services.Common.RESTRequest DEBUG GET https://xyz.example.com:16666/token/1.0/sync/1.5 401 1599203778898 Services.Common.TokenServerClient DEBUG Got token response: 401 1599203778898 Services.Common.TokenServerClient INFO Server-reported error: {"location":"body","name":"","description":"Unauthorized"} 1599203778899 Services.Common.RESTRequest DEBUG POST request to https://api.accounts.firefox.com/v1/oauth/destroy 1599203778899 Services.Common.RESTRequest DEBUG POST Length: 969 1599203778900 FirefoxAccounts DEBUG _updateAccountData with items: ["oauthTokens"] 1599203778900 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778900 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1599203778901 Sync.BrowserIDManager ERROR Authentication error in _fetchTokenForUser: {"details":{"now":"2020-09-04T07:16:18.898Z","message":"Authentication failed.","cause":"invalid-credentials","response_body":"{\"status\": \"invalid-credentials\", \"errors\": [{\"location\": \"body\", \"name\": \"\", \"description\": \"Unauthorized\"}]}","response_headers":{"server":"nginx/1.14.0 (Ubuntu)","date":"Fri, 04 Sep 2020 07:16:18 GMT","content-type":"application/json; charset=UTF-8","content-length":"110","x-weave-timestamp":"1599203778.14","x-timestamp":"1599203778","x-firefox-spdy":"h2"},"response_status":401,"name":"TokenServerClientServerError"},"s

Any news out here? We would like to use the sync again. It does not work in our whole company anymore

It's better to file a bug directly on Bugzilla. Then you can paste your bug URL here, so we could follow it.

Thank you! I found a solution that worked for me:

https://superuser.com/questions/1583196/firefox-80-no-persistend-login-not-syncing-with-own-sync-server

I'm very sure i already used the syncserver 1.8 because i installed it one month ago but a fresh reinstall including the commit e1aab54 seems to work. I just needed to do the following steps (after stopping the syncserver)

cd /opt mv /opt/syncserver /opt/syncserver.bak git clone https://github.com/mozilla-services/syncserver.git cd /opt/syncserver git checkout e1aab54cbcb6e570979835789f7b4624eebdc875 make build cp /opt/syncserver.bak/syncserver.ini /opt/syncserver/syncserver.ini cp /opt/syncserver.bak/syncserver.db /opt/syncserver/syncserver.db

now starting the server again.

Not sure if the special commit fixed the issue. i did the exact same steps one month ago -excluding the git checkout.

Thanks fpr infomation about 80.0.1. Actually I block all updates. You say "Server 1.8" ? I still have 1.5 from here: https://mozilla-services.readthedocs.io/en/latest/howtos/run-sync-1.5.html

I do not really want to build a new server because i am not a linux specialist. So it was hard enought to build the server on my Pi using this (german) manual:

https://jankarres.de/2014/07/raspberry-pi-firefox-sync-server-installieren/

It is without git (I have no clue about git) So i am afraid to destroy all if I try to fix it with a new version :(

I would prefer mozilla to fix the problem. Or is giving me a working, ready-for-use solition sync-server (linux, windows)

But thnks for the hint about superuser.com

Well...lets see what I am about to do.

@Moderator/Admin: Can someone please change the Topic from "Syncserven" to "Syncserver"? (typo)

@TyDraniu Ok. Will try to do so later.

It is without git (I have no clue about git) So i am afraid to destroy all if I try to fix it with a new version :(

@firefox938: I used syncserver 1.5 up to now on my Raspberry Pi. My Firefox version is 81.0.1, actually. I use it on Ubuntu 20.04, Windows 10 and Android. None of these had problem with this syncserver version. I installed it with Jan's tutorial. Today I changed to syncserver 1.8. I did not anything else as User35123 wrote: Stop your syncserver, rename the directory, clone the version 1.8 and build it. It worked without any problem. There is a warning about python 2.7 which is out of service, that's all. Copy the syncserver.ini, probably the database (I don't have the syncserver.db, I am using a mysql database), start the server. Don't be afraid. Even you have a problem while building and you give up: Just delete the directory, and rename the old directory again. You will not destroy anything.