Jump to content

Emby connect with "Report https as external address"


inzombyac
Go to solution Solved by inzombyac,

Recommended Posts

inzombyac

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.

Link to comment
Share on other sites

inzombyac

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

Edited by inzombyac
Link to comment
Share on other sites

inzombyac

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

Link to comment
Share on other sites

inzombyac

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

inzombyac

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.

Link to comment
Share on other sites

inzombyac

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?

 

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • Solution
inzombyac

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.  

  • Like 1
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
×
×
  • Create New...