Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Search 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.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Sync login window is empty

  • 1 èsì
  • 1 ní ìṣòro yìí
  • 3 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ pucicu

more options

Hello, I have problems to login into the Firefox-Sync process. After the last update I have a yellow line at the bottom of the browser window that states that there is a sync problem and that the password would be invalid. After pressing the buttom "Preferences" I can go to the preferences panel, but after clicking the "login" button, I only get an empty page (see attached figure, where I have collected the three screenshots of this process). My system is a Mac with OSX 10.9.5, Firefox is 41.0, I tested with running but disabled Noscript plugin. Any idea how I can reactive the login? BTW: the login data have not changed. I can still login on the sync-sebsite at https://accounts.firefox.com Thanks! Norbert

Hello, I have problems to login into the Firefox-Sync process. After the last update I have a yellow line at the bottom of the browser window that states that there is a sync problem and that the password would be invalid. After pressing the buttom "Preferences" I can go to the preferences panel, but after clicking the "login" button, I only get an empty page (see attached figure, where I have collected the three screenshots of this process). My system is a Mac with OSX 10.9.5, Firefox is 41.0, I tested with running but disabled Noscript plugin. Any idea how I can reactive the login? BTW: the login data have not changed. I can still login on the sync-sebsite at https://accounts.firefox.com Thanks! Norbert

Ọ̀nà àbáyọ tí a yàn

Just after posting the question I found out that the noscript plugin was not disabled. Disabling the plugin solved the problem.

Sorry for the question.

Ka ìdáhùn ni ìṣètò kíkà 👍 0

All Replies (1)

more options

Ọ̀nà àbáyọ Tí a Yàn

Just after posting the question I found out that the noscript plugin was not disabled. Disabling the plugin solved the problem.

Sorry for the question.