Søg i 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.

Læs mere

Firefox sync fails to connect to the server.

  • 1 svar
  • 16 har dette problem
  • 1 visning
  • Seneste svar af hshar

more options

Firefox sync has not been working on my laptop for the past few days. It fails with the error "Failed to connect to the server. Sync will automatically retry this action." Sync is working fine on my Android device on the same network. I tried to disconnect and reconnect my sync account and also tried to sync in safe mode without any success. The error report from the sync log: https://pastebin.mozilla.org/8834320. In about:config the services.sync.clusterURL is not set. services.sync.tokenServerURI is set to the default value "https://token.services.mozilla.com/1.0/sync/1.5"

Firefox sync has not been working on my laptop for the past few days. It fails with the error "Failed to connect to the server. Sync will automatically retry this action." Sync is working fine on my Android device on the same network. I tried to disconnect and reconnect my sync account and also tried to sync in safe mode without any success. The error report from the sync log: https://pastebin.mozilla.org/8834320. In about:config the services.sync.clusterURL is not set. services.sync.tokenServerURI is set to the default value "https://token.services.mozilla.com/1.0/sync/1.5"

Valgt løsning

Figured out the problem. I had enabled FIPS compliance on my software security device. Apparently, WeaveCrypto used by sync does not support FIPS. I have disabled FIPS now and sync is working fine. Related bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=443386

Læs dette svar i sammenhæng 👍 1

Alle svar (1)

more options

Valgt løsning

Figured out the problem. I had enabled FIPS compliance on my software security device. Apparently, WeaveCrypto used by sync does not support FIPS. I have disabled FIPS now and sync is working fine. Related bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=443386