Emby connect with "Report https as external address"

[inzombyac 69]

Is the Roku client compatible with the server option "Report https as external address"?  I have been unable to make this work from outside my network using Emby connect.  I have 3 family members with Roku 3's.  When I enable this setting, they are able to see my server but when they click on it it says it is unable to connect.  If I turn it off, everything works fine.  I am using a certificate from letsencrypt if that matters.  Getting log files from there will be a challenge, so I am looking to see if this setup is supported before trying anything else.

 

Interestingly, if I go to https://tv.emby.media, the reverse occurs.  I can only use Emby connect on the web if I have the option checked.

[ebr 16178]

Hi.  On what platform is your server running?

[inzombyac 69]

@ebr: The server is a windows machine (Windows 7) with the current stable release 3.2.17.0.

Edited May 18, 2017 by inzombyac

[inzombyac 69]

This also fails with the new app.  Instead of a connection error, the system acts like it is loading and stays there.

[Luke 42078]

Interestingly, if I go to https://tv.emby.media, the reverse occurs.  I can only use Emby connect on the web if I have the option checked.

 

That's not true. You would use http://tv.emby.media

 

A web app under https cannot communicate with http addresses.

[inzombyac 69]

That's not true. You would use http://tv.emby.media

 

A web app under https cannot communicate with http addresses.

 

I assumed that the option "Report https as external address"? would just set the preferred mode.  If the setting means it exclusively uses https that would make sense.  In any event, I can't switch over to https with this problem.

[ebr 16178]

So your original report was with the older version of the Roku app?

[inzombyac 69]

Yes, this has been an issue for over a year now.  The behavior is a bit different in the new version, but my users are unable to connect.  All 3 have the 2014 or 2015 Roku 3.  At the time I was using the self-signed certificate so I figured that was the issue.  I am using a letsencrypt cert now and was hoping that would solve it.

[inzombyac 69]

I picked up a Roku to help troubleshoot this issue. I setup a new wireless network on a separate LAN to replicate the same environment as my users. When I use Emby Connect with HTTPS it doesn't connect and sends me back to select a server screen.  If I manually try to add a server with the HTTPS information, I get an error:

Error connecting to:
-60: SSL certificate problem: unable to get local issuer certificate

So it seems it doesn't like using Letsencyrpt certificates.  I setup a new Emby server on another machine to test.  This time I used the standard self signed certificate.  In that case I get:

Error connecting to:
-60: SSL certificate problem: self signed certificate

Is there any way to make this work free with Letsencrypt or do I need to find another issuer?

 

[ebr 16178]

Are your server installs all on Linux variants?  There is a known problem with mono not passing the entire certificate chain but it can be worked around with manual intervention.

[inzombyac 69]

Both installs are Windows based (7 & 8).

[inzombyac 69]

Was able to finally fix this myself. Leaving this here in case it helps anyone else. I suspected that the certificate chain was not being served up. Since I use letsencrypt-win-simple, I followed the guide here: https://github.com/Lone-Coder/letsencrypt-win-simple/wiki/Missing-Certificate-Chain.  Now I am finally able to connect.  

[ebr 16178]

Thanks very much for the investigation.