SSL not working with tv.emby.media or app.emby.media

[kjp4756 41]

I cannot get SSL working with the emby connect web clients (both tv and app).  SSL is properly configured on my server using letsencrypt.  I can connect to my server both LAN and WAN using SSL just fine.  No certificate errors of any kind.

 

When trying to access my server through either site it says it cannot connect.  HTTP works fine.  When attempting with HTTPS through either app.emby.media or tv emby.media I don't even see a connection attempt on my server using tcpdump.

 

The only thing I can think of that could be a problem is the letsencrypt certificate is domain name bound.  If I access emby using SSL through my WAN IP I get a certificate error.  Using the domain works with no error.

[kjp4756 41]

Ok, so if I go to https://app.emby.media and click on my server called "Emby Server" I get a message saying it cannot connect to the server.  I then click on the Add Server button.  Type in https://emby.mydomain.com and put 8920 in the port.  I then click OK and I connect successfully.

 

Why can't I just chose "Emby Server" instead of having to manually enter the address and port?  I thought that was the point of emby connect.

 

EDIT: Got it working.  Needed to enable "Report https as external address" in emby server.  Makes sense now that I think about it.  Emby connect uses what ever address is listed under "Remote access".

Edited March 3, 2016 by kjp4756

[Luke 37102]

This may negatively affect other apps though

[kjp4756 41]

Web client appears to be fine.  That was going to be my main client.  I may also use my chromecast externally.  Any issues with chromecast and ssl?  I am using a valid certificate so I would think it would work.

[Luke 37102]

You'll have to try it out. i think others here in the community have posted results with that, but I don't recall right now.

[kjp4756 41]

Haven't been able to test chromecast yet but the android beta clients appears to work fine over ssl, including playback.  I was surprised that the android client worked.  I thought I had read there had to be changes to libvlc for this.  Maybe that was about using self signed ssl certificates; i can't remember.