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

Firefox Sync is not working

more options

Hello.

It seems Firefox Sync is not working in my country. Here is the sync-log contents: https://pastebin.com/zhEqEV1E

I think, The reason is the government at 16th of April '18 started blocking operation of Telegram messenger in my country, but they have no luck at this, so They just blocked a huge piece of the Internet for us. And the FF Sync too.

Any help?

Hello. It seems Firefox Sync is not working in my country. Here is the sync-log contents: https://pastebin.com/zhEqEV1E I think, The reason is the government at 16th of April '18 started blocking operation of Telegram messenger in my country, but they have no luck at this, so They just blocked a huge piece of the Internet for us. And the FF Sync too. Any help?

Chosen solution

Hello everyone. I have the solution.

I just had the random http proxy set up in my FF's settings. After sync was OK, I set the proxy off. Now I am kinda have "sync on demand".

I dont think there is a guilt of my employer. We re a small company and we dont have an IT dept.

As I said earlier, government in my country have blocked millions of IP-adresses on 16th of April, and the first error-log occured exactly at that day. That is what happen in my opinion.

Thanks to everyone here!

Read this answer in context 👍 0

All Replies (9)

more options

Hi, this has been reported to a Supervisor and please wait to be contacted by next week latest. Thank You.

more options

Hey there,

Thank you for the pastebin, I am getting second opinion on your errors, can you provide the last 5 error log files from about:sync-logs ?

The insufficient storage usually mean you have reached the max. For now, disable the syncing of add-ons and see if you can complete a full sync.

With the newest sync logs we can take a look to make sure nothing else is happening. I look forward to your reply!

more options

Hello. Thanks for helping me with my problem.

Was experiencing troubles with getting access to about:sync-log but now its fine :)

Here is the last six error-logs(last five are from today): https://pastebin.com/4tusug4h https://pastebin.com/Mztv7cJP https://pastebin.com/dC0DqqY2 https://pastebin.com/nNKavTaY https://pastebin.com/rDYRdgtr https://pastebin.com/4UWV97pr

I have disabled addons sync both on my computers at home and at work, but it brings no effect.

I am ready to follow your further instructions.

Modified by AlexanderRhu

more options

And more, I have just found accounts.firefox.com is not responding for me(checked via ping).

more options

cor-el said

Is the about:sync-log page available via the about:about page? The about:about lists all available about: protocol pages.

Yes thank you, I have just mistyped and tryed about:sync-logs, but now everything OK with that

more options

Hello everyone, good news here.

I digged out my old laptop, and FF sync on it(ofc its updated) is working fine, including bookmarks.

So the question is why its not working at my work computer(not in my country :))

Modified by AlexanderRhu

more options

Hi

It may be the case that your employers IT support team have disabled that functionality. I recommend that you contact them for guidance on this issue.

more options

Seburo said

Hi It may be the case that your employers IT support team have disabled that functionality. I recommend that you contact them for guidance on this issue.

I have seen it mentioned a few times here that a person's employer was blocking their users from using the Sync service.

more options

Chosen Solution

Hello everyone. I have the solution.

I just had the random http proxy set up in my FF's settings. After sync was OK, I set the proxy off. Now I am kinda have "sync on demand".

I dont think there is a guilt of my employer. We re a small company and we dont have an IT dept.

As I said earlier, government in my country have blocked millions of IP-adresses on 16th of April, and the first error-log occured exactly at that day. That is what happen in my opinion.

Thanks to everyone here!