Disable ports on WAN connections

[fstropii 0]

Hey! I am currently using NGINX Proxy Manager to handle all my reverse proxies. One of my issues with Emby that I have encountered so far is forcing public ports on WAN connections. NPM (NGINX Proxy Manager) handles port resolving, so forcing ports results in my domain not being accessible in Emby Connect. If I had the ability for Emby to just resolve "https:emby.example.com", that would fix all my issues. I can understand why ports on WAN is needed for some users, but for users like me who use NPM, forcing ports on WAN results in the loss of Emby Connect. Thank you for reading! 

[Luke 42077]

Hi, this should be supported already, just not with Emby Connect. When you enter connection info into an Emby app, you should be able to leave the port blank.

[darkassassin07 652]

 

Set this to the port NPM is listening on.

 

The server will tell clients to use the port specified there when connecting from WAN using https.

[fstropii 0]

Thank you so much! That worked, I don't know why I didn't think to use that earlier, but thanks again.