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

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

RESOLVED: Unable to Sync, Bad Request

  • 1 wotmołwa
  • 3 maja tutón problem
  • 76 napohladow
  • Poslednja wotmołwa wot sheldon.dedek

sheldon.dedek
sheldon.dedek

Newly restored Lenovo factory image. 2 pieces 3rd party sw: Atlas (v0.4.1 9Oct2024) and Firefox 133.0. Windows 10 22H2, no updates pending, Edge / Cortana / CoPilot removed (by Atlas).

FF sync account is recognized, sends auth code to email, when enter code, get the: "Bad Request Something went wrong. Please close this tab and try again." at each attempt.

Oddly, I have 2FA enabled, and have not been queried for its code. Perhaps that is where process is failing?

Another Lenovo machine, M710Q 1TB 16GB Windows 22H2 with Atlas, Firefox 133.0 and a slew of 3rd party software and updates is running just fine. Am able to sync / manipulate account as needed, FF Relay, etc.

Suggestions / tips before I nuke the M920Q and start from scratch again?

Newly restored Lenovo factory image. 2 pieces 3rd party sw: Atlas (v0.4.1 9Oct2024) and Firefox 133.0. Windows 10 22H2, no updates pending, Edge / Cortana / CoPilot removed (by Atlas). FF sync account is recognized, sends auth code to email, when enter code, get the: "Bad Request Something went wrong. Please close this tab and try again." at each attempt. Oddly, I have 2FA enabled, and have not been queried for its code. Perhaps that is where process is failing? Another Lenovo machine, M710Q 1TB 16GB Windows 22H2 with Atlas, Firefox 133.0 and a slew of 3rd party software and updates is running just fine. Am able to sync / manipulate account as needed, FF Relay, etc. Suggestions / tips before I nuke the M920Q and start from scratch again?

Wot sheldon.dedek změnjeny

Wšě wotmołwy (1)

sheldon.dedek
sheldon.dedek Prašer

Resolved, kind of.

Signed back into account, looked at security tab and saw the multiple entries saying account sign in failed.

Refreshed 2FA, same thing. Disabled 2FA. Deleted off 2FA app. Re-enabled 2FA, creating QR code, backup codes, etc.

Went to add sync again, same procedure: User name, password, email auth code but then it asked for the 2FA auth code. And successfully completed. Now have access to passwords and bookmarks that I use across various devices.

Ideal Solution: Ask for 2FA up front if account exists, redirect to verify 2FA prior to starting sync process.

As mozilla / ff are able to see that I am logging into an account, why not ask for 2FA when adding new device? Perhaps refresh / disable / enable allowed account to be 'updated' with 2FA usage despite having used it in the past?