07-24-2016 12:05
07-24-2016 12:05
I have been using my Fitbit Zip for several years now. For the past 24+ hours I have not been able to sync. I keep getting the "Server is Busy" message and have tried restarting my Mac, but still cannot sync. Is anyone else having this issue or does anyone else have a solution??? Thank you!!
07-24-2016 13:07
07-24-2016 13:07
I've had the same problem. I have de-installed the software, downloaded another version from the fitbit site and re-installed. Since doing that earlier today I have had one successful synch, shortly after re-installing. But now, for several hours, I have been getting the "server appears to be busy" message. Very frustrating. The problem must be at the fitbit end, rather than with our trackers.
07-24-2016 15:45
07-24-2016 15:45
Sorry to hear that you are having issues too, but it does make me feel a bit better to know I'm not alone!! Hope this resolves itself soon - don't want to lose all of my steps!!!!
07-24-2016 17:33
07-24-2016 17:33
07-25-2016 09:08
07-25-2016 09:08
Ever since July 21st I've been getting the "Server appears to be busy" message. On Friday the 22nd I called customer service and was told not to worry, that the problem was on their end and that the server was undergoing maintenance and that the problem might continue until today, Monday the 25th. If that was the case I have a couple of problems: 1. Why not tell fitbit users upfront that there is a short-term issue with the server instead of making us waste our time seeking answers to this large glitch? 2. Now that it is Monday and the problem has not been resolved... we continue to be left in the dark as to the nature of the issue and when, if ever, this will be fixed.
This is really frustrating. My girlfriend has a "One" and a macbook pro. I have a "Zip" and an iMac. We are both running OS X El Capitan and have had no problems until last week. Any answers, Fitbit?
07-25-2016 10:24
07-25-2016 10:24
It seems that many of us using Mac computers are having this problem, which appeared out of the blue in the last few days. The Fitbit software people need to figure this out, as clearly the problem is on their end. The software currently available for Fitbit Connect does not work. Under the Fitbit Connect symbol in the toolbar, the Sync now, and Open Main Menu, as well as Wireless Sync Dongle Connected are all "grayed out". The older version of the Fitbit Connect (for Mac, 10.5) gives the never-ending "server appears to be busy" message. I haven't had any reply yet to my email messages to Fitbit Help.
07-25-2016 10:58
07-25-2016 10:58
Thanks for commiserating, jer52. I did a fairly lengthy live chat after leaving my earlier post. The person with whom I was chatting had no idea that there was any sort of problem. Eventually, it was suggested that I restart my computer (again) but this time without the dongle plugged in. Guess what? It didn't help! Somewhere else in the "Help" pages, uninstalling and reinstalling "Fitbit Connect" was suggested as a solution to various problems. I don't know if that would mean a loss of my 3 years of data. Nor do I know if it would actually fix the problem. I am hesitant to chance it. Sure would be nice to get some conclusive answers from Fitbit
07-25-2016 16:42
07-25-2016 16:42
Thank you for posting! I too thought that it was just mine. I walked my butt off to win a challenge and no sync 🙂 but at least I am not lying lol.
07-26-2016 15:12
07-26-2016 15:12
Sorry for the trouble, everyone! We recognize that syncing and setup were not completing successfully over the past few days for customers using older versions of Fitbit Connect. You should now be able to sync normally.
If you're still having difficulty syncing, please check the troubleshooting tips in this help article.
07-31-2016 15:59
07-31-2016 15:59
Finally, today, my Zip is syncing manually. After waiting a few days, I once again de-installed Fitbit Connect, cleared my machine, shut down, restarted, downloaded the old version of Fitbit Connect for Mac (version for system 10.5), and re-installed. Restarted again. And voila, it worked. I had done all of this several times before today, to no avail, despite the message from the Help folks that everything had been fixed. Makes me really wonder what had caused the problem.