Smaky 131 Posted July 22, 2015 Share Posted July 22, 2015 I am having issues with both Emby for Android and Emby for Android TV apos while trying to access through a WAN connection. I have no issues accessing Emby from the WAN using Firefox or Chrome for Android (via https). In my setup I have a my public address mapped as https://myserver.publicvm.com (using a free DynDNS service). Web client works just fine. However trying to login from Emby for Android using the https://myserver.publicvm.com on Host and Port 8920 ends up with "We´re unable to connect to the selected server right now.." That same exact web address used in Chrome would work nicely. Client will work just fine when connected to my local WiFi network. Link to comment Share on other sites More sharing options...
jjspierx 11 Posted July 29, 2015 Share Posted July 29, 2015 Are you using the latest versions of the Android and Android TV apps? I use the Android app to connect over WAN using DynDNS and https and it works fine for me. Not sure if it matters, but I don't use UPnP, I manually forward the ports in my router. Maybe there is an issue with the UPnP configuration of the apps, that your browsers don't experience. Might be worth trying, manually forwarding the ports to see if it works. Link to comment Share on other sites More sharing options...
Solution Oakington 13 Posted July 31, 2015 Solution Share Posted July 31, 2015 I don't think there is HTTPS support for android yet. I was working on getting it integrated to the native android app and actually succeeded but that was about the time Luke switched over to Cordova. Android doesn't like self signed certificates. Nor Chromecast. I gave up for now due to the latter. It should work once letsencrypt.org gets going. Once live, I'm going to take a stab at serverside integration of letsencrypt, but that's still a few months out. 1 Link to comment Share on other sites More sharing options...
Smaky 131 Posted August 2, 2015 Author Share Posted August 2, 2015 Thanks, I was not aware of the fact that the Andriod app does not yet support https. I will patiently wait until it is implemented and may help debugging it when it is implemented. Link to comment Share on other sites More sharing options...
Luke 37113 Posted August 2, 2015 Share Posted August 2, 2015 it should work if you have a trusted cert, but not self signed. Link to comment Share on other sites More sharing options...
NahsiN 0 Posted August 10, 2015 Share Posted August 10, 2015 (edited) Ah glad to see that others are having this issue and people are working on it. I wait . Great work guys and gals btw! Also letsencrypt seems interesting. Thanks for the link Edited August 10, 2015 by NahsiN Link to comment Share on other sites More sharing options...
runtimesandbox 153 Posted August 11, 2015 Share Posted August 11, 2015 Ah this explains why i couldnt get it to work. Will this work in ios or will we need a trusted cert? Link to comment Share on other sites More sharing options...
ivoidwarranties 15 Posted August 12, 2015 Share Posted August 12, 2015 (edited) it should work if you have a trusted cert, but not self signed. @Luke: I am using a trusted cert. I only have one cert for my server -- with different web applications on different context / path (ex: https://secure.mydomain.com/app1, https://secure.mydomain.com/app2, https://secure.mydomain.com/emby, etc). When I try to access https://secure.mydomain.com/emby on a web browser, it works like a champ. But when I try it on the Android Emby app, it never connects outside of my network. Looking at the logs on my Android device, it looks like the Emby app does not use the /emby or /mediabrowser context when attempting to connect: com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112) 15:08:18.707 [JavaBridge] INFO App - event.trigger response8 15:08:18.709 [JavaBridge] INFO App - event.off response8 15:08:18.711 [JavaBridge] INFO App - connectToAddress https://secure.mydomain.com:443 failed 15:08:31.743 [JavaBridge] INFO App - tryConnect url: https://secure.mydomain.com:443/system/info/public 15:08:31.745 [JavaBridge] INFO App - Sending request: {"Method":"GET","Url":"https://secure.mydomain.com:443/system/info/public","RequestHeaders":{"accept":"application/json"},"Timeout":20000} 15:08:31.760 [JavaBridge] DEBUG App - Adding request to queue: https://secure.mydomain.com:443/system/info/public 15:08:31.762 [JavaBridge] INFO App - event.on response9 15:08:31.980 [main] ERROR App - VolleyError com.android.volley.ServerError: null Is there a way to force the Emby Android app to use the /emby or /mediabrowser context? When I try to configure it through the Emby app, I get this error in the log: com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:112) 15:07:12.095 [JavaBridge] INFO App - event.trigger response5 15:07:12.097 [JavaBridge] INFO App - event.off response5 15:07:12.101 [JavaBridge] INFO App - connectToAddress https://secure.mydomain.com/mediabrowser/:443 failed 15:07:15.889 [JavaBridge] INFO App - tryConnect url: https://secure.mydomain.com/mediabrowser/:443/system/info/public 15:07:15.892 [JavaBridge] INFO App - Sending request: {"Method":"GET","Url":"https://secure.mydomain.com/mediabrowser/:443/system/info/public","RequestHeaders":{"accept":"application/json"},"Timeout":20000} 15:07:15.906 [JavaBridge] DEBUG App - Adding request to queue: https://secure.mydomain.com/mediabrowser/:443/system/info/public 15:07:15.909 [JavaBridge] INFO App - event.on response6 15:07:16.118 [main] ERROR App - VolleyError com.android.volley.ServerError: null ----------------------------------------------------- EDIT / SOLVED (?): Never mind... got it to work by not entering a port number (leave it blank). Everything appears to be working now... will play around with it some more and report back. Edited August 12, 2015 by ivoidwarranties 1 Link to comment Share on other sites More sharing options...
Luke 37113 Posted August 13, 2015 Share Posted August 13, 2015 Well done. Link to comment Share on other sites More sharing options...
mortstar 2 Posted September 4, 2015 Share Posted September 4, 2015 (edited) EDIT: Posted my own topic: /25077-using-reverse-proxy-login-fail/ Edited September 4, 2015 by mortstar Link to comment Share on other sites More sharing options...
vick1982 15 Posted November 22, 2015 Share Posted November 22, 2015 hi... so with the android app it will only work when you have a trusted certificate with the above method of not entering a port number ? Link to comment Share on other sites More sharing options...
ri4naire 0 Posted January 11, 2016 Share Posted January 11, 2016 I wanted to add that I struggled with this until I chained in the root certificate. This is a little contradictory to your statement since technically a root cert is always a self signed certificate. Just glad I got it working now though! it should work if you have a trusted cert, but not self signed. Link to comment Share on other sites More sharing options...
jkotecki 0 Posted March 16, 2016 Share Posted March 16, 2016 I'm having the same problem. I am using a trusted cert. I imported the whole cert chain and I am able to connect externally using a browser just fine. The Android app however will only connect using port 8096. Link to comment Share on other sites More sharing options...
anderbytes 139 Posted March 16, 2016 Share Posted March 16, 2016 I'm having the same problem. I am using a trusted cert. I imported the whole cert chain and I am able to connect externally using a browser just fine. The Android app however will only connect using port 8096. To connect to interface via Android you also have to import the p12 version of that pfx into your android device. About the playback via https on android, it is a known bug, because libVLC still can't use the pfx that Emby uses. Link to comment Share on other sites More sharing options...
Ge0rge 1 Posted October 19, 2016 Share Posted October 19, 2016 Hi! Can I donate my lifetime subscription to resolve this issue? Link to comment Share on other sites More sharing options...
Luke 37113 Posted October 19, 2016 Share Posted October 19, 2016 Hi! Can I donate my lifetime subscription to resolve this issue? Hi, welcome. Can you please describe your issue in detail? Thanks ! Link to comment Share on other sites More sharing options...
Ge0rge 1 Posted October 24, 2016 Share Posted October 24, 2016 the same as the topic - unable to connect from Android app over https. "Request was denied for security" appears. Link to comment Share on other sites More sharing options...
Luke 37113 Posted October 24, 2016 Share Posted October 24, 2016 Are you running your own ssl cert or the default self signed cert? Link to comment Share on other sites More sharing options...
Ge0rge 1 Posted October 25, 2016 Share Posted October 25, 2016 (edited) I use the default self signed cert as it was installed from repo. Looks like the Emby Theatre Windows Metro app doesn't like https also, am I right? Edited October 26, 2016 by Ge0rge Link to comment Share on other sites More sharing options...
Luke 37113 Posted October 26, 2016 Share Posted October 26, 2016 I use the default self signed cert as it was installed from repo. Looks like the Emby Theatre Windows Metro app doesn't like https also, am I right? It supports https but self signed certs are always tricky. Devices are going to reject them by default so we have to look at what workarounds are possible to allow them. We'll review this for a future release of the app. Thanks. Link to comment Share on other sites More sharing options...
nwcatalyst 4 Posted December 26, 2016 Share Posted December 26, 2016 I was able to connect via Android over Lets Encrypt HTTPS when using Emby Connect (after linking the server to my Emby Connect locally). It kept giving me errors (denied for security reasons) when attempting to connect manually... Seems odd as this used to work with the same config to a different server, but for anyone still searching I recommend linking the server to Emby Connect and then trying to sign into the server via Android that way vs manual connection. Link to comment Share on other sites More sharing options...
fgs 0 Posted May 13, 2017 Share Posted May 13, 2017 Greetings. Thanks for reading this. I purchased the Emby Android for TV a while ago. I had OpenVPN in place for that device but now I'd like to switch to more adequate HTTPS secure via 8920 (default suggested). After a brief struggle to enter the URL at my Android apps running on my smartphone and tablet devices (thanks to useful info here at the forum), I managed to get them working right but not for the TV app. Simple as that, is the Android TV currently supporting HTTPS via 8920 port? Thanks. Link to comment Share on other sites More sharing options...
ebr 14929 Posted May 13, 2017 Share Posted May 13, 2017 Hi. This will only work with a true signed certificate that can be accepted by the Android TV device (like LetsEncrypt). It won't work with the default self signed cert that comes with the server. Does that help? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now