I can't seem to sync. I've tried numerous times over the last two days.
I'm using Mac OS X 10.4.6, Firefox 1.5.0.4. The only other Firefox extensions installed are the DOM inspector 1.8.0.4, del.icio.us 1.1, FoxTunes 1.2.5.
I'm using DSL.
I see the "Updating server" message in the progress indicator, but a minute or so later I receive the error message "Error 51 'Request time out.
This happens even when Firefox is the only open application.
I do have many bookmarks, mostly sorted into folders; I'd estimate several hundred bookmarks, but less than a thousand.
> I see the "Updating server" message in the progress indicator, but a > minute or so later I receive the error message "Error 51 'Request time > out.
Had the same problem -- Firefox 1.5.0.4 w/scads of extensions, WinXP SP2, trying to sync only bookmarks (encrypted); however, I just got it to work.
Here's what I did (not that I'm suggesting it as a step-by-step instruction set), in case it's helpful for troubleshooting:
1) First, I tried disabling every single one of my extensions except for google bookmark sync. Still didn't work.
2) Next, I both uninstalled the bookmark sync plugin from Firefox and deleted it from my google account.
3) I re-installed the bookmark sync plugin, set my options (bookmarks encrypted, nothing else). Worked the very first time.
4) re-enabled all my extensions, restarted firefox with no problems. Went into bookmark sync, did a full refresh, went through just fine.
So, not sure exactly where the problem lies -- however, I'm guessing it's not related to the other extensions; I'm wagering that if I have the problem again, uninstalling the bookmark sync plugin, restarting firefox, then re-installing it might take care of it for me. But, maybe not, who knows what weird voodoo happens under the hood when you have a complex app with two dozen plugins from different developers all doing stuff :)
Andrew wrote: > > I see the "Updating server" message in the progress indicator, but a > > minute or so later I receive the error message "Error 51 'Request time > > out.
> Had the same problem -- Firefox 1.5.0.4 w/scads of extensions, WinXP > SP2, trying to sync only bookmarks (encrypted); however, I just got it > to work.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060527 SUSE/1.5.0.4-0.1 Firefox/1.5.0.4
SuSE10.1.
Ended up getting it working by deleting my browser sync account. Also accepted default settings, vs encrypting the lot.
> I can't seem to sync. I've tried numerous times over the last two days.
> I'm using Mac OS X 10.4.6, Firefox 1.5.0.4. The only other Firefox > extensions installed are the DOM inspector 1.8.0.4, del.icio.us 1.1, > FoxTunes 1.2.5.
> I'm using DSL.
> I see the "Updating server" message in the progress indicator, but a > minute or so later I receive the error message "Error 51 'Request time > out.
> This happens even when Firefox is the only open application.
> I do have many bookmarks, mostly sorted into folders; I'd estimate > several hundred bookmarks, but less than a thousand.
I have a similar problem using FF 1.5.0.4 and WinXP SP2.
For me, the sync process gets to "updating server" - it actually uploads a couple of hundred KBs of data (or so my upload meter says) then stalls and gives me a "A '400 Bad request' error happened". When I click on OK, the window closes and FF starts, but obviously the GoogleSync icon is telling me it's offline.
Funnily enough, it DID sync partially. For example, I installed the extension on another computer (same software configuration) that runs the same extensions, and there it worked just fine from the get-go. It let me store bookmarks etc. via Google Sync on the first try. It even imported this on the computer where I've been having problems with the extension. It also imported the bookmarks from the non-working computer onto the other one, even though it kept telling me it couldn't sync there.
So I'm still mystified to why this is happening. Seems it's partially doing the synchronization after all. I also tried just enabling single sync categories, but all gave me the same error.
More precise error messages could really benefit tracking down errors like this.
