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 Android not syncing with hosted sync server

  • 7 replies
  • 1 has this problem
  • 12 views
  • Last reply by pilou2

more options

Hello everyone,

I successfully configured my own Firefox sync server on a Ubuntu server with Apache2. (see https://mozilla-services.readthedocs.io/en/latest/howtos/run-sync-1.5.html#howto-run-sync15) It syncs OK between different Firefox client (Linux, Windows 10...) but not with Android version. I configured the identity.sync.tokenserver.uri like on the desktop versions by looking at about:config. I double-verified configuration, but nothing sync. All the checkbox are grayed (see attached images) As there isn't sync log like on desktop versions (about:sync-log), I looked at my Apache log instead, and it seems that something goes wrong. Indeed, when a desktop client starts to sync, there are lines like: 192.xxx.xxx.xxx - - [23/May/2020:18:48:50 +0200] "GET /token/1.0/sync/1.5 HTTP/1.1" 200 3122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0" or 77.xxx.xxx.xxx - - [23/May/2020:06:54:40 +0200] "GET /token/1.0/sync/1.5 HTTP/1.1" 200 3122 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0" but when android client starts to sync, it seems that url is incomplete (there isn't /token/1.0/sync/1.5 after GET): 92.xxx.xxx.xxx - - [22/May/2020:21:03:45 +0200] "GET / HTTP/1.1" 200 2579 "-" "Mozilla/5.0 (Android 6.0.1; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0" I suspect this is the problem, but I can't understand why. Your help would be greatly appreciated! Thanks a lot in advance.

Pascal

Hello everyone, I successfully configured my own Firefox sync server on a Ubuntu server with Apache2. (see https://mozilla-services.readthedocs.io/en/latest/howtos/run-sync-1.5.html#howto-run-sync15) It syncs OK between different Firefox client (Linux, Windows 10...) but not with Android version. I configured the identity.sync.tokenserver.uri like on the desktop versions by looking at about:config. I double-verified configuration, but nothing sync. All the checkbox are grayed (see attached images) As there isn't sync log like on desktop versions (about:sync-log), I looked at my Apache log instead, and it seems that something goes wrong. Indeed, when a desktop client starts to sync, there are lines like: 192.xxx.xxx.xxx - - [23/May/2020:18:48:50 +0200] "'''GET /token/1.0/sync/1.5 HTTP/1.1'''" 200 3122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0" or 77.xxx.xxx.xxx - - [23/May/2020:06:54:40 +0200] "'''GET /token/1.0/sync/1.5 HTTP/1.1'''" 200 3122 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0" but when android client starts to sync, it seems that url is incomplete (there isn't /token/1.0/sync/1.5 after GET): 92.xxx.xxx.xxx - - [22/May/2020:21:03:45 +0200] "'''GET / HTTP/1'''.1" 200 2579 "-" "Mozilla/5.0 (Android 6.0.1; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0" I suspect this is the problem, but I can't understand why. Your help would be greatly appreciated! Thanks a lot in advance. Pascal
Attached screenshots

All Replies (7)

more options

Hello, no idea of my problem ? Thanks in advance.

more options

Hello, Oh... My subject seem to be uninteresting... What a pitty !

more options

Hi

I am sorry for the delay in getting to your question. Please appreciate that we are mostly volunteers here and your question is a little non-standard.

I have asked for help from our developers and hope to have an answer soon.

more options

Hi

I have heard back from our developers who have noticed that you appear to be using the existing Firefox for Android.

We are due to roll out a significant update to this copy of Firefox very soon which may resolve the issue that you are seeing.

more options

Hi Seburo,

thanks a lot for your reply ! I'm aware that there are mostly mostly volunteers here and my question is a bit non standard. So, I'm waiting for the new version to test it. Thanks you so much for your help. Best regards,

Pascal

more options

No problem, thank you for your support.

more options

Hello Seburo, hello to everybody, so, I installed the last beta version (80.0) on my Android phone, and the problem is identical. (I used beta version because release version doesn't allow access to about:config) What a pity ! Wait and see if developers will find the problem. Thanks a lot in advance.

Pascal