rcmpayne 0 Posted March 31, 2019 Share Posted March 31, 2019 I have setup Reverse proxy setup with Letsencrypt/NGINX Unraid and when i go to emby.domain.com 80 or 443, it redirects to SSL and hits my nginx config correctly and up comes Emby remotely without issue. https://emby.media/community/index.php?/topic/47508-how-to-nginx-reverse-proxy/ My next question is what changes do i now need to do on Router for port forwarding and on Emby Advance section? For my Router i still have 8096 and 8920 set as a port forward to emby directly. Can i remove these now and still expect remote users to start using 443 method? On the advance hosting page in Emby, what correct settings do i need now? Lan Network: 192.168.0.0/24, 10.0.8.0/24 Bind to Local Address: 192.168.0.100 Local http port number: 8096 Local https port number: 8920 Allow Remote connections: Enabled? Remote IP: Blank Remote IP Filter Mode: Whitelist Public HTTP Port: 8096 - is this needed anymore? Public HTTPS Port: 8920 - is this needed anymore? External Domain: emby.domain.com Custome SSL Server: not needed and Nginx is proxying to Local IP over 8096? Secure connection mode: Reverse Proxy or not needed My understanding that with Nginx redirect, emby no longer needs any access to external internal but how would users and external apps know to go to emby.domain.com using 443? Link to comment Share on other sites More sharing options...
Luke 36889 Posted March 31, 2019 Share Posted March 31, 2019 Hi, yes you still need to fill out those values because that is how Emby apps will determine your remote address for remote connections. Please let us know if this helps. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now