Jump to content

Cannot connect over HTTPS WAN


Smaky
 Share

Go to solution Solved by Oakington,

Recommended Posts

Smaky

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

jjspierx

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

  • Solution
Oakington

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. 

  • Like 1
Link to comment
Share on other sites

Smaky

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

  • 2 weeks later...

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 by NahsiN
Link to comment
Share on other sites

runtimesandbox

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

ivoidwarranties

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 by ivoidwarranties
  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...
  • 2 months later...
vick1982

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

  • 1 month later...
ri4naire

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!  :D

 

it should work if you have a trusted cert, but not self signed.

Link to comment
Share on other sites

  • 2 months later...
jkotecki

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

anderbytes

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

  • 7 months later...

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

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 by Ge0rge
Link to comment
Share on other sites

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

  • 1 month later...
nwcatalyst

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

  • 4 months later...

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

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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...