External domain name

[mastrmind11 722]

When adding an external domain name to the appropriate field under Advanced on the server dashboard, the result is the domain name w/ 8096 appended to the end and the port in the domain name is stripped.  Since this is an Advanced setting, I assumed I would be able to specify my own port (ie, 443 or 80) and let my router/proxy do the work.  As it stands now, I have to open 8096 and redirect it to my proxie's port 443.  Not a huge deal, just thought I'd bring it up.

[dcrdev 255]

Not sure I understand what your saying here, but is this what you want?:

 

[mastrmind11 722]

Not sure I understand what your saying here, but is this what you want?:

 

Yes, that.  I let nginx handle my SSL so if I have to muck w/ the Emby SSL settings to get it to work, I'll just deal with it as is.

 

edit:  but generally speaking, being able to choose whatever port I want in my external address would be better imo.

Edited February 15, 2018 by mastrmind11

[dcrdev 255]

Yes, that.  I let nginx handle my SSL so if I have to muck w/ the Emby SSL settings to get it to work, I'll just deal with it as is.

 

edit:  but generally speaking, being able to choose whatever port I want in my external address would be better imo.

 

You can do that...

 

Have you seen my answer here:

https://emby.media/community/index.php?/topic/55484-help-with-reverse-proxycustom-domain-and-remote-connectivity/

[mastrmind11 722]

You can do that...

 

Have you seen my answer here:

https://emby.media/community/index.php?/topic/55484-help-with-reverse-proxycustom-domain-and-remote-connectivity/

Ok I see.  I will give it a whirl after work.  Thanks

 

Also, I assume since my container is running in host mode that I don't need to flip the IsBehindProxy bit (since I can already access the server externally)?

[dcrdev 255]

Ok I see.  I will give it a whirl after work.  Thanks

 

Also, I assume since my container is running in host mode that I don't need to flip the IsBehindProxy bit (since I can already access the server externally)?

 

Yes and no.

 

Depends whether you want to force ssl - which requires one of two configurations:

1. RequireHttps enabled - but this requires you to have installed a cert into Emby. You probably don't want this as this will create twice the overhead if your proxy is handling ssl.
2. RequireHttps disabled, EnableHttps enabled and IsBehindReverseProxy enabled. This will force https for all clients without having configured ssl in Emby. The IsBehindReverseProxy is required here otherwise it just reports the standard http address. It's weird, but I think @@Luke mentioned something about bringing these options back into the GUI - so hopefully it might get a clean up at the same time.