Completed External Connections - Force HTTPS

[James W 7]

In a recent server update the advanced section for hosting changed. This has caused a bit of an issue for me and possibly other people that are using a reverse proxy for Emby

 

Before I was able to show the external address as the domain I input and the custom port I use. I am using IIS to proxy and do SSL offloading. 

 

IIS is programmed to work on the internal IP over http X.X.X.X:8096

 

My external connection is my domain xxx.xxxx.xxx:custom port  

 

The issue becomes if i checkbox the "Require https for external connections" it will update the remote address to the proper one but then my SSL offloading does not work as all requests are being redirected to https on the Emby server

 

It seems that one of my remote clients a Kodi box actually automaticlly updated the server address to the wrong one because Emby is reporting the wrong external address to clients. 

 

Can the option to use a custom external address and port be returned without forcing https on the Emby server?

Edited January 20, 2018 by James W

[Luke 37045]

Hi, yes we'll look at this,thanks.

[James W 7]

Thank you Luke!!

[Swynol 375]

@@James W

 

leave the require HTTPS box unticked. You need a valid PFX cert and password - fill the emby boxes with them. The boxes need to be filled even though we wont be using them!

 

then edit the emby system.xml 

 

look for something like - 

 

<enableHTTPS>false</enableHTTPS>

 

change it to true and restart emby server.

 

it will now report the correct HTTPS://blahblah:443 in the dashboard. point your reverse proxy to the local HTTP port. this way IIS manages the SSL part.

Edited January 22, 2018 by Swynol

[James W 7]

@@Swynol awesome thank you for the info. It is working great!

Edited February 3, 2018 by James W