Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Learn More

Sync keeps losing password.

  • 4 respostas
  • 1 tem este problema
  • 117 visualizações
  • Última resposta por ams.fwd

more options

Every so often (almost every restart) Sync complains that it failed because the password was bad. On clicking on the yellow status bar at the bottom, I enter the same password and it all works... until it seems to lose it again.

I do use private browsing on a daily basis. Firefox is not set to clear history on exit, although third-party cookies are set to clear on every exit. Sync settings are preserved, just that password appears to be messed up.

Every so often (almost every restart) Sync complains that it failed because the password was bad. On clicking on the yellow status bar at the bottom, I enter the same password and it all works... until it seems to lose it again. I do use private browsing on a daily basis. Firefox is not set to clear history on exit, although third-party cookies are set to clear on every exit. Sync settings are preserved, just that password appears to be messed up.

Todas as respostas (4)

more options

Is the correct password saved in the password manager?

  • Edit > Preferences > Security: Passwords: "Saved Passwords" > "Show Passwords"

Also make sure that only one entry appears.

You can find the Password of the Sync account and the Sync Key in the password manager on computers where have setup that sync account with a specific e-mail address.

Look for:

  • chrome://weave (Mozilla Services Password)
  • chrome://weave (Mozilla Services Encryption Passphrase)
more options

Yes. Only the two you mentioned above are present. Mozilla Services Password is correct and the Encryption Passphrase appears to some alphanumeric code.

The username seems to be some alphanumeric code too.

more options

Yes, that is correct. The user name internally is also some kind of hash string data, but you can always use the e-mail address to connect to a sync account.

Does this only happen if Private Browsing mode is enabled?

Does Safe mode has any effect?

more options

In both cases I get the same error.

From the logs: ~/.mozilla/firefox/default/weave/logs/error-*

1357192864601	Sync.Service	INFO	Loading Weave 1.19.0
1357192864609	Sync.Engine.Bookmarks	DEBUG	Engine initialized
1357192864609	Sync.Engine.Forms	DEBUG	Engine initialized
1357192864610	Sync.Engine.History	DEBUG	Engine initialized
1357192864611	Sync.Engine.Passwords	DEBUG	Engine initialized
1357192864611	Sync.Engine.Prefs	DEBUG	Engine initialized
1357192864611	Sync.Engine.Tabs	DEBUG	Engine initialized
1357192864612	Sync.Engine.Tabs	DEBUG	Resetting tabs last sync time
1357192864612	Sync.Engine.Addons	DEBUG	Engine initialized
1357192864613	Sync.Service	INFO	Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0
1357192864615	Sync.SyncScheduler	DEBUG	Clearing sync triggers and the global score.
1357192864615	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192864616	Sync.Service	DEBUG	Caching URLs under storage user base: https://scl2-sync1005.services.mozilla.com/1.1/---------------------------------/
1357192864616	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192864616	Sync.AddonsReconciler	INFO	Registering as Add-on Manager listener.
1357192864616	Sync.AddonsReconciler	DEBUG	Adding change listener.
1357192864619	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192864620	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192870593	Sync.SyncScheduler	DEBUG	Next sync in 90000 ms.
1357192873621	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192873621	Sync.SyncScheduler	DEBUG	Next sync in 86379 ms.
1357192873720	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192874803	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192877919	Sync.ErrorHandler	DEBUG	Beginning user-triggered sync.
1357192877920	Sync.Service	DEBUG	User-Agent: Firefox/17.0.1 FxSync/1.19.0.20121128204232.
1357192877920	Sync.Service	INFO	Starting sync at 2013-01-02 22:01:17
1357192877920	Sync.Service	DEBUG	In sync: should login.
1357192877921	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192877922	Sync.Status	DEBUG	Status.service: success.status_ok => success.status_ok
1357192877922	Sync.Service	INFO	Logging in user ---------------------------------
1357192877922	Sync.Service	DEBUG	Caching URLs under storage user base: https://scl2-sync1005.services.mozilla.com/1.1/---------------------------------/
1357192877939	Sync.Resource	DEBUG	Channel redirect: https://scl2-sync1005.services.mozilla.com/1.1/---------------------------------/info/collections, https://scl2-sync1005.services.mozilla.com/1.1/---------------------------------/info/collections, 4
1357192878072	Sync.Resource	DEBUG	mesg: GET fail 401 https://scl2-sync1005.services.mozilla.com/1.1/---------------------------------/info/collections
1357192878072	Sync.Resource	DEBUG	GET fail 401 https://scl2-sync1005.services.mozilla.com/1.1/---------------------------------/info/collections
1357192878072	Sync.Service	WARN	401: login failed.
1357192878073	Sync.Service	DEBUG	Finding cluster for user ---------------------------------
1357192878376	Sync.Resource	DEBUG	mesg: GET success 200 https://auth.services.mozilla.com/user/1.0/---------------------------------/node/weave
1357192878376	Sync.Resource	DEBUG	GET success 200 https://auth.services.mozilla.com/user/1.0/---------------------------------/node/weave
1357192878377	Sync.Service	DEBUG	Cluster value = https://scl2-sync1005.services.mozilla.com/
1357192878377	Sync.Status	DEBUG	Status.login: success.login => error.login.reason.account
1357192878377	Sync.Status	DEBUG	Status.service: success.status_ok => error.login.failed
1357192878378	Sync.SyncScheduler	DEBUG	Clearing sync triggers and the global score.

Modificado por ams.fwd a