Jump to content

Bug (I think) when turning on HTTPS


BillOatman
Go to solution Solved by Luke,

Recommended Posts

BillOatman

Hi.  For years I have not had https enabled. I have had during that time, 2 of my kids accessing the server remotely with no issue. One uses his xbox and the other her firestick. Both have used Emby Theater as well.  Everything has worked fine.

This is what shows in that mode in the dashboard (IP redacted).

image.png.030597384112e6e21734c79d1dd05bb9.png

 

I wanted to play with chefs alexa plugin which needs https on.  So I enabled it, and set this under network

image.png.48def2ab57252bd951744b39d569f913.png

Restarted Emby.  Neither kid could connect.  The error message they get is Connection failure. We're unable to connect to the selected server right now.

I looked at the dashboard and it shows this  I did have to install a certificate on the emby server for the alexa plugin.

image.png.94b9e0396a17e82b7df8bb61ecb97926.png

IP redacted again, but now notice it only shows remote access via https, which is also the behavior I see. When I changed the secure connection mode back to disabled the dashboard switched back to the first screenshot and they could connect to the server again.

So is the preferred mode not working correctly (sure looks that way to me in appearance as well as behavior)?  Or is there something that needs to be done on the remote apps when https is enabled on the server?

Thanks!

Link to comment
Share on other sites

Hi, as soon as you set it to preferred, that is the address your Emby Server will advertise to Emby apps. Your users can still connect with plain http, but they will need to enter the address manually into the app in order to do that.

Link to comment
Share on other sites

BillOatman
32 minutes ago, Luke said:

Hi, as soon as you set it to preferred, that is the address your Emby Server will advertise to Emby apps. Your users can still connect with plain http, but they will need to enter the address manually into the app in order to do that.

Thanks.  But if its advertised to the apps, shouldn't they connect via https then? They are using emby connect.

Edited by BillOatman
Link to comment
Share on other sites

It sounds like they are trying and not able to. You will need to choose your SSL certificate carefully based on what your client devices will trust and accept.

Link to comment
Share on other sites

Q-Droid

Are you redacting an IP addr or domain name for the WAN access in that image? You want a domain name that matches the certificate subject (CN) or SAN. Otherwise what is sent to client apps as a preferred connection link will not match the certificate name presented during handshake.

It's the "External domain:" field in the Network settings.

 

  • Like 1
Link to comment
Share on other sites

rbjtech

I think the point the OP is making is even if https does not work (for whatever reason), it should drop back to http that does as they have set 'preferred, not required.

Edited by rbjtech
  • Like 1
Link to comment
Share on other sites

BillOatman
41 minutes ago, rbjtech said:

I think the point the OP is making is even if https does not work (for whatever reason), it should drop back to http that does as they have set 'preferred, not required.

Yes this is my assumption on how it would work when I selected Preferred.  How its acting now is what I would call Required.

My use case is I need https in order for Amazon to be able to send Alexa commands to the Alexa Emby plugin (the one by @chef),  but I don't want to screw around with certificates on my kids remote devices and have them still use Emby Connect.

@Luke Is there a way to accomplish my use case currently?

Link to comment
Share on other sites

50 minutes ago, BillOatman said:

How its acting now is what I would call Required.

It isn't required as you can still connect manually with http.  

Link to comment
Share on other sites

  • Solution
2 hours ago, BillOatman said:

Yes this is my assumption on how it would work when I selected Preferred.  How its acting now is what I would call Required.

My use case is I need https in order for Amazon to be able to send Alexa commands to the Alexa Emby plugin (the one by @chef),  but I don't want to screw around with certificates on my kids remote devices and have them still use Emby Connect.

@Luke Is there a way to accomplish my use case currently?

Automatically, no, but it's a possible improvement for the future. thanks.

Link to comment
Share on other sites

BillOatman
4 hours ago, ebr said:

It isn't required as you can still connect manually with http.  

Semantics I suppose, but to use Emby Connect HTTPS is required in this case.

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...