Reverse-Proxy and Remote access URL

[HumanPanda 5]

Hi,

 

I have emby set up with a nginx reverse proxy and it is working great. The only issue I am having so far is the Remote access URL. Since my emby server is hosted on server.com/emby and the public https is set to 443, when you have it broadcast the https for external, the remote access url becomes invalid because it becomes server.com/emby:443. I think this is important for the phone apps to work and such would need it so it could become server.com:443/emby or just omit 443 as that is the standard https port.

 

Is there anyway to do this?

Edited March 12, 2016 by phiyuku

[Bonfi 2]

Hi, 

I'm using nginx as well as a reverse proxy with https, and I don't  have this problem.

Could you post you nginx conf?

[HumanPanda 5]

Hi Bonfi.

 

Are you using a subfolder or on the root of it? As mine is /emby to get there. I have no issue with the root as I am currently having another issue where emby does not serve the entire chain of the SSL cert and am forced to use another nginx listener to serve it on the root of the subdomain on a different port and it works.

 

I am using the same nginx as the one found here:

 

http://emby.media/community/index.php?/topic/22889-emby-behind-a-reverse-proxy-remote-control-issue/

 

post#5

 

Thanks.

Edited March 16, 2016 by phiyuku

[Cerothen 89]

I also use nginx as my reverse proxy without rewriting so when connecting to /emby it also connects to /emby on the backend server.

 

@@Luke mentioned that eventually all the apps will be using the /emby path to better support mobile apps however not all of them do at this time.

 

There was another post somewhere that indicates if you wanted to connect from an app externally you should just leave the port empty and type the full url into the host field eg https://domain.TLD/emby

 

This has been working for me for a while now without issue

[benbar21 0]

Hi,

 

I have emby set up with a nginx reverse proxy and it is working great. The only issue I am having so far is the Remote access URL. Since my emby server is hosted on server.com/emby and the public https is set to 443, when you have it broadcast the https for external, the remote access url becomes invalid because it becomes server.com/emby:443. I think this is important for the phone apps to work and such would need it so it could become server.com:443/emby or just omit 443 as that is the standard https port.

 

Is there anyway to do this?

 

Hey!

 

Did you ever figure it out? I have the exact same issue!

 

Thanks