Hi Jerry, On Fri, Dec 4, 2015 at 9:14 AM, Jerry Chapman <[email protected]> wrote:
> I generated a free certificate with https://letsencrypt.org/ this morning > and tried to get this working again. I have been successfully accessing a > server using a publicly accessible URL over port 22443 with SSL for a long > time now on a Fedora machine with my Windows Firefox computer. I have been > unable to access it from my Android phone until today when I put it on the > standard 443 port. > Thrilled that you're using Let's Encrypt! I'm about to fetch a certificate myself. 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. 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. Thanks for the report! Nick
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
