Completed Allow for empty port field

[KMBanana 84]

I have a reverse proxy and am using that to make Emby available remotely at https://sub.domain.XYZ/NotEmby

 

I recently tried to experiment with with Emby on Kodi on my phone, but could not get it to connect remotely at all.  I eventually discovered the following workaround that made it work.

If I set the server address to "https://sub.domain.XYZ"and the port to "/NotEmby" it connected and worked perfectly.  

 

What didn't work was any combination of either the full URL with either http or https and port 80, 443, 0, or 00000.  

 

I'm assuming what's throwing this off is my nginx config to make /NotEmby work, but I don't know a better way to do it. 

rewrite /NotEmby/(.*) /$1 break;

Including a port doesn't seem necessary when using a URL and port 80 or 443, so why force it to be set during the configuration?  

[thatoneguy99 33]

Just doing some thinking about this and how do you have your reverse proxy set up? Wouldn't you have tied the /notemby address to the service that is running on the Emby port that you set up in the configuration? Without a port, what would you attach your reverse proxy too?

 

I know on my Emby app I am able to connect using the full URL and leaving the port blank. I only use Kodi on my HTPC so i connect to localip:port. I can't speak on trying to use Kodi remotely, but I just had those questions and wanted to ask.

[KMBanana 84]

Just doing some thinking about this and how do you have your reverse proxy set up? Wouldn't you have tied the /notemby address to the service that is running on the Emby port that you set up in the configuration? Without a port, what would you attach your reverse proxy too?

 

I know on my Emby app I am able to connect using the full URL and leaving the port blank. I only use Kodi on my HTPC so i connect to localip:port. I can't speak on trying to use Kodi remotely, but I just had those questions and wanted to ask.

Emby is running with the default port 8096.  But I don't have port 8096 publicly exposed.  

 

The reverse proxy is listening on the default web ports 80 and 443, passing traffic for /notEmby to port 8096.  

[pir8radio 1292]

I have a reverse proxy and am using that to make Emby available remotely at https://sub.domain.XYZ/NotEmby

 

I recently tried to experiment with with Emby on Kodi on my phone, but could not get it to connect remotely at all.  I eventually discovered the following workaround that made it work.

If I set the server address to "https://sub.domain.XYZ"and the port to "/NotEmby" it connected and worked perfectly.  

 

What didn't work was any combination of either the full URL with either http or https and port 80, 443, 0, or 00000.  

 

I'm assuming what's throwing this off is my nginx config to make /NotEmby work, but I don't know a better way to do it. 

rewrite /NotEmby/(.*) /$1 break;

Including a port doesn't seem necessary when using a URL and port 80 or 443, so why force it to be set during the configuration?  

 

Again, you will always have an issue with one app or another using a subdirectory.  Subdomains are cleaner... even if you already have a sub domain, most dynamic dns services will allow you to enter another sub domain...    https://emby.sub.domain.com/    

 

either way I would expect your rewrite location to look like:  tomato tamato.... 

location /NotEmby/ {                                          #note the backslash after emby
                rewrite ^/NotEmby(/.*)$ $1 break;             #this will strip /emby from the requests going into emby backend

Edited November 2, 2017 by pir8radio

[KMBanana 84]

I might switch my setup to use subdomains soon when LetsEncrypt supports wildcard certs since I do know they are less prone to weird issues like this.  Should be only a few months away.  

 

But for anyone else experiencing this edge case I think the application setup should allow the user to go forward with a blank Port field entry.  

[Angelblue05 4130]

But for anyone else experiencing this edge case I think the application setup should allow the user to go forward with a blank Port field entry.  

I'll make the necessary changes. Thank you.