On Fri, Dec 4, 2015 at 1:06 PM, Nicholas Alexander <[email protected]>
wrote:

> What version of Firefox for Android are you using?  I recall an old bug in
> this area -- https://bugzilla.mozilla.org/show_bug.cgi?id=1046020 -- but
> that should be in place for everything past Firefox 33.  In addition, if
> you're using new versions of Firefox for Android, the situation has changed
> and I haven't updated the documentation.  Sorry for this.
>

Android version 42.0.2


> It's possible to see what service endpoints Firefox for Android is trying
> to reach using |adb logcat|.  See
> http://160.twinql.com/how-to-file-a-good-android-sync-bug/ for notes on
> using |adb logcat|.
>
> The problem seems to be that the Android client does not recognize the
>> non-standard port.  It says my application URL is https://myserver.com
>> and that the public URL is https://myserver.com:22443.  Changing the
>> server to listen on 443 and fixing this on Android Firefox solves the
>> problem and the device syncs successfully.
>>
>> I used the information from this blog to get things rolling:
>> http://www.ncalexander.net/blog/2014/07/05/how-to-connect-firefox-for-android-to-self-hosted-services/
>>
>> Is this a bug in the Firefox plugin?  The server listens on the
>> non-standard port as a way to prevent unwanted https traffic.  I'd like to
>> do this if I could.
>>
>
> It's more likely to be a bug in Firefox for Android itself than the
> add-on, but it's hard to know a priori.  It sounds like you're witnessing
> traffic on 443 when you want 22443.  Using |adb logcat| would help us see
> if the add-on is producing the correct URLs.
>
> I'll take an action item to update the documentation, since significant
> changes are riding the trains.  I have a ticket tracking this --
> https://bugzilla.mozilla.org/show_bug.cgi?id=1205801 -- but it's private
> because there are raw user numbers.  I'll try to get that opened, or file
> another public ticket.
>
>
Here is the adb logcat output showing the error.  As you can see, the
application URL and the public URL are different.  I have the 54443 port
forwarded on my router to my server at port 443.  This has never been a
problem with Windows Firefox sync.  I have also tried listening on port
54443 on the server and just forwarded the port directly to make sure this
wasn't an issue.

Sorry for the change in port number.  I have been experimenting and didn't
keep it the same this time.  Everything else is the same.

https://pastebin.mozilla.org/8853913

Thanks for your quick response!

Jerry
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev

Reply via email to