Avatar for Username

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

This thread was archived. Jei jums reikia pagalbos, užduokite naują klausimą.

Invalid URL Errors when trying to access custom Sync Server(rev 532) from Firefox 17.0 for Android via HTTPS

Takahide Matsuoka
Takahide Matsuoka
more options

I currently have Sync Server(rev 532) installed on FreeBSD-STABLE(stable/9) and have Firefox 17 on Mac OS X and Windows XP sync successfully. But when I try to pair Firefox 17.0 for Android by entering 3 rows of 4 letter codes into Firefox on Desktop, the sync never ends on Android, although the Sync account gets listed in "Settings> Accounts & sync> Firefox Sync". If I try to pair the Android with advanced setting (using the Recovery Key), I get "Please enter valid server URL" after entering custom server URL (I tried mozsync.mydomain.tld, https://mozsync.mydomain.tld, https://mozsync.mydomain.tld/) along with my account information. I had my Sync Server listen on HTTPS only, but if I setup my server on HTTP, everything works as expected. The content of log file for SSL connection only includes the logs from my Desktop and none from my Android device. Direct access from Firefox for Android to "https://mozsync.mydomain.tld/weave-delete-account" succeeds, and this connection gets logged. My device is HTC Evo 4G (named HTC EVO WiMAX ISW11HT in Japan) with officially updated of version Android (2.3.4 Gingerbread :P) by HTC.

I currently have my Sync Server listening on HTTP, but I am little uncomfortable with my syncing datas being tranmitted without SSL. Any help is appreciated!!!

I currently have Sync Server(rev 532) installed on FreeBSD-STABLE(stable/9) and have Firefox 17 on Mac OS X and Windows XP sync successfully. But when I try to pair Firefox 17.0 for Android by entering 3 rows of 4 letter codes into Firefox on Desktop, the sync never ends on Android, although the Sync account gets listed in "Settings> Accounts & sync> Firefox Sync". If I try to pair the Android with advanced setting (using the Recovery Key), I get "Please enter valid server URL" after entering custom server URL (I tried mozsync.mydomain.tld, https://mozsync.mydomain.tld, https://mozsync.mydomain.tld/) along with my account information. I had my Sync Server listen on HTTPS only, but if I setup my server on HTTP, everything works as expected. The content of log file for SSL connection only includes the logs from my Desktop and none from my Android device. Direct access from Firefox for Android to "https://mozsync.mydomain.tld/weave-delete-account" succeeds, and this connection gets logged. My device is HTC Evo 4G (named HTC EVO WiMAX ISW11HT in Japan) with officially updated of version Android (2.3.4 Gingerbread :P) by HTC. I currently have my Sync Server listening on HTTP, but I am little uncomfortable with my syncing datas being tranmitted without SSL. Any help is appreciated!!!

Chosen solution

I have filed a bug here at bugzilla. Any help is still appreciated!!!

Edit: The bug was filed as duplicate of this. It turned out the CA, which issued my certificate, was not bundled and importing SSL is broken in early version of Android. Same applies to self-signed certificates. Maybe the solution is to update the Android version by rooting the phone, which is not my choice.

I'm closing my question as solved, because the root of the problem is not Firefox.

Skaityti atsakymą kartu su kontekstu 👍 0

All Replies (1)

Takahide Matsuoka
Takahide Matsuoka Klausimą uždavęs asmuo
more options

Chosen Solution

I have filed a bug here at bugzilla. Any help is still appreciated!!!

Edit: The bug was filed as duplicate of this. It turned out the CA, which issued my certificate, was not bundled and importing SSL is broken in early version of Android. Same applies to self-signed certificates. Maybe the solution is to update the Android version by rooting the phone, which is not my choice.

I'm closing my question as solved, because the root of the problem is not Firefox.

Modified by Takahide Matsuoka