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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Every time I restart my Firefox browser, my Sync information has gone and I need to re-set up Sync

  • 2 antwoorde
  • 11 hierdie probleem
  • 5 views
  • Laaste antwoord deur wouna

more options

When I set up Sync using my sync key (via the "Set Up Sync..." option in the Firefox 5 menu), everything works fine and all of my data is synced. However, when I close my browser and re-open it, the "Set Up Sync..." now reappears and the browser is no-longer synced.

Any ideas?

When I set up Sync using my sync key (via the "Set Up Sync..." option in the Firefox 5 menu), everything works fine and all of my data is synced. However, when I close my browser and re-open it, the "Set Up Sync..." now reappears and the browser is no-longer synced. Any ideas?

Gekose oplossing

Hi wouna,

If you have configured your browser to clean up the browsing history after closing the browser, the Sync configuration is also erased. This is something known and will be solved in the future.

In the meantime you can tell Firefox to remember your configuration after closing in the custom configuration of your privacy settings.

I hope it helps.

Lees dié antwoord in konteks 👍 5

All Replies (2)

more options

Gekose oplossing

Hi wouna,

If you have configured your browser to clean up the browsing history after closing the browser, the Sync configuration is also erased. This is something known and will be solved in the future.

In the meantime you can tell Firefox to remember your configuration after closing in the custom configuration of your privacy settings.

I hope it helps.

more options

Of course! That makes sense if weave stores the passwords in the password manager. The 'bug' also occurs, it seems, if you have permanent private browsing mode enabled; although, in my opinion, it's not so much a 'bug' as this behaviour is to be expected when you think about it.

Thanks for the tip!