Emby https with Nginx Proxy Manager

[espoulin 0]

No matter what I try, I cannot access my Emby server with https.

I have both Nginx Proxy Manager and Emby running on the same server. I have a certificate created for embyserveraddress.duckdns.org and created a proxy host pointing to the local http address for my emby server 192.168.1.99 with port 8096

In Emby network settings:

Local http port number: 8096
Local https port number: 8920
Allow remote connections to this Emby Server: checked
Public http port number: 80
Public https port number: 443
External domain: embyserveraddress.duckdns.org
Secure connection mode: handled by reverse proxy

In my router, because I have Nginx Proxy Manager to use port 90 instead of 80 and port 450 instead of 443, I forwarded those in my router so that Int port for 192.168.1.99 is 90 and Ext is 80, and Int port 450 is forwarded to Ext port 443.

When I try https://embyserveraddress.duckdns.org I get "The site can't be reached" and ERR_HTTP2_PROTOCOL_ERROR. If I try http://embyserveraddress.duckdns.org I get Congratulations! You've successfully started the Nginx Proxy Manager. If you're seeing this site then you're trying to access a host that isn't set up yet. Log in to the Admin panel to get started.

I'm not sure how to set this up.

[Luke 42077]

Hi, have you taken a look at this?

 

[espoulin 0]

No, but it turns out that it's a problem with NPM. I have another server with working NPM, and I set things up on there and it works perfectly. Sorry for the post.

[Luke 42077]

That's interesting. Thanks for the feedback.

[pir8radio 1312]

On 8/23/2022 at 1:55 PM, espoulin said:

No, but it turns out that it's a problem with NPM. I have another server with working NPM, and I set things up on there and it works perfectly. Sorry for the post.

curious did you find something?    I hear quite a few people complaining about emby not working when they use NPM... curious if you found something i could post in the nginx config to help other NPM users?

[brintal 0]

On 8/23/2022 at 8:55 PM, espoulin said:

No, but it turns out that it's a problem with NPM. I have another server with working NPM, and I set things up on there and it works perfectly. Sorry for the post.

Could you be so kind and post the working NPM config? I'm still struggling with this.

[bigverm23 2]

Anyone ever get this working with npm?

[Lambtalk 44]

23 minutes ago, bigverm23 said:

Anyone ever get this working with npm?

I have it working in NPM. I didn't need to do anything special.

Click Add Proxy Host

Details tab:

- Domain Names: yourdomainname

- Scheme: http

- Foward Hostname / IP: the IP address of your Emby server

- Forward Port: 8096 (unless you've changed the port you use expose Emby over http)

- Tick Block Common Exploits and Websockets Support

 

SSL tab:

- SSL Certificate: select your already generated certificate, or choose to generate a new one

- Tick Force SSL, HTTP/2 Support, HSTS Enabled and HSTS Subdomains

Click Save

[bigverm23 2]

hmmm, yeah this doesnt work for me when trying to access emby externally though.  Only way I can do it is from mobile by entering the server as "https:emby.domainname.com" with the port blank.  Problem is that Roku and Firestick force you to enter a port.

 

do you mind sharing your network settings inside of Emby?

Edited May 24, 2023 by bigverm23

[Lambtalk 44]

5 minutes ago, bigverm23 said:

hmmm, yeah this doesnt work for me when trying to access emby externally though.  Only way I can do it is from mobile by entering the server as "https:emby.domainname.com" with the port blank.  Problem is that Roku and Firestick force you to enter a port.

 

do you mind sharing your network settings inside of Emby?

Enter the port as 443, as that is the default https port that is being used when you call a https:// website.

 

[bigverm23 2]

dagnabbit I think that change to 443 did it!!

[Lambtalk 44]

1 hour ago, bigverm23 said:

dagnabbit I think that change to 443 did it!!

Awesome! I'm glad I could help get that resolved for you