FF Sync: Wrong password but it is the correct password.

[Credomane]

Binary package hint: firefox

Updated from package version 4.0.1+build1+nobinonly+0ubuntu0.11.04.3 (natty-updates) to 5.0.+build1+nobinonly+0ubuntu0.11.04.1 (natty-proposed).

Not even sure why a Firefox beta is in the proposed updates anyways. The real release isn't until June 21st but whatever. ;)

Now firefox sync will not work. Claims my password is incorrect even if I completely retype it. The "Saved Passwords" shows the correct password both before and after retyping my password. I'm quite confused as to what is going on. All 3 of my other computers running Firefox 4.0.1 are still syncing just fine. If it makes a difference I'm not using the add-on but the built-in sync client.

Let me know if there is anything else you need from me. I'll be glad to help.

[Felix Wohlfrom (felix-wohlfrom)]

Same here. Works fine on firefox < 5.0 on both win and ubuntu and after update to 5.0 it says that the password is wrong.
I don't use the mozilla but the minimal wave server [1] on my own machine.
Don't know if mozilla changed something in the password hashing algorithm, but it's really annoying because I use firefox sync really often to sync my bookmarks and tabs between various systems and os'es.

[1] http://tobyelliott.wordpress.com/2009/09/11/weave-minimal-server/

[Felix Wohlfrom (felix-wohlfrom)]

Update:
As mentioned here [1] I just had to change the version checking string in the minimal server and it was working again.

[1] http://tobyelliott.wordpress.com/2011/04/12/api-version-change-coming-in-aurora/

[Credomane (credomane)]

I'm already running 1.1 which is why I thought it to be a firefox 5 problem. My initial setup was a 1.1 minimal install and everything had been working fine until now.

I found the problem. Even though I copied the information out of the readme, I made a mistake in correcting the file path for the 1.1 alias but typed it correctly for the 1.0 alias. Since everything had been working I never thought to check that until you pointed out the 1.0 -> 1.1

I'm an idiot and going to mark this bug as invalid.