
Firefox Android not syncing with hosted sync server
Hello everybody,
I hope you're doing well in theses days, and your health is good ! A few months ago, I installed with success my own Firefox sync server. It is working like a charm with both desktop Windows and Linux version, but it doesn't work with Android version. I discovered that the client try to reach a bad URL (see my preceding post: https://support.mozilla.org/en-US/questions/1288028). Moreover, with the last version, we can't modify anymore the identity.sync.tokenserver.uri In the Nightly version, this parameter isn't present. Have we any chance to use Firefox android version with a custom sync server ? Thanks a lot in advance for your help.
Pascal
Chosen solution
Hello, I finally found an answer, and I was right: the issue was due to my server's self-signed certificate. Indeed, I use now a Let's encrypt certificate instead (see https://letsencrypt.org/fr/getting-started/), and the android client syncs every time without trouble. Very interesting. I will see in next days if there will be other issues, but there is no reason. So my problem could interest other people in the same case ;) Thanks a lot,
Pascal
Read this answer in context 👍 0All Replies (7)
Hi Pascal
In the Nightly version of Firefox for Android, open the menu and scroll down to About Firefox Nightly.
Tap the logo five times (a message should appear), go back to Settings and underneath your account you should see two new options to help set a custom sync server.
I hope that this helps.
Hi Seburo, I just tried: the problem is the same. I looked at my Apache logs, Firefox on Android ask an incomplete URL: 192.168.1.254 - - [27/Dec/2020:20:55:03 +0100] "GET / HTTP/1.1" 200 2579 "-" "Mozilla/5.0 (Android 8.1.0; Mobile; rv:86.0) Gecko/86.0 Firefox/86.0" instead of: 192.168.1.254 - - [27/Dec/2020:20:59:12 +0100] "GET /token/1.0/sync/1.5 HTTP/1.1" 200 3122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0" for desktop version. Have you an idea ?
Hello, Very strange thing happened: this morning, my girlfriend and I were in her car moving to do grocery shopping, and I was surfing on Firefox Nightly, then checked the history and remarked something new: Firefox has been synchronized ! When we returned to our home, I checked in Apache log, and confirmed that Firefox Nightly has been synchronized: 92.xxx.xxx.49 - - [28/Dec/2020:09:08:22 +0100] "GET /token/1.0/sync/1.5 HTTP/1.1" 200 3122 "-" "Mozilla/5.0 (Android 8.1.0; Mobile; rv:86.0) Gecko/86.0 Firefox/86.0" But now it didn't synchronize anymore, neither with mobile network, nor with wifi. URL isn't correct ! 92.xxx.xxx.104 - - [28/Dec/2020:15:47:32 +0100] "GET / HTTP/1.1" 200 2579 "-" "Mozilla/5.0 (Android 8.1.0; Mobile; rv:86.0) Gecko/86.0 Firefox/86.0" Very strange isn't it ?
I must admit that I do not know too much about self hosting a sync server - I have never tried it.
Cn we assume that this issue is resolved? Feel free to come back to us if it is not working.
Hello, I have a clue, but not 100% sure. My server is using a self signed certificate. To make the synchronization working, first I have to open the server page. The first time, Firefox informs me about potential security risk, then I must accept certificate and do a permanent exception. It's the same thing with desktop version. It seems that Android Firefox Nightly doesn't make the exception permanent. I just tried and asked me again to accept certificate. How can I make it permanent ?
Hi
I recomend that you contact the Firefox Account experts direcly in their Matrix room at https://chat.mozilla.org/#/room/#fxa:mozilla.org
They will know much more than me and should be able to help you there.
Chosen Solution
Hello, I finally found an answer, and I was right: the issue was due to my server's self-signed certificate. Indeed, I use now a Let's encrypt certificate instead (see https://letsencrypt.org/fr/getting-started/), and the android client syncs every time without trouble. Very interesting. I will see in next days if there will be other issues, but there is no reason. So my problem could interest other people in the same case ;) Thanks a lot,
Pascal