bigverm23 2 Posted January 19, 2019 Posted January 19, 2019 I have since moved Emby Server off of docker and into my local linux host on 192.168.1.99. Since I have the rest of my media apps running in a docker host though, using traefik as a reverse proxy they are all accessible via https://app.domain.com (using Let's Encrypt certs) What I would like to do is still reverse proxy emby server using a separate rules.toml file, which I have successfully done for FreeNAS, Unifi, and Ubuntu VM. [backends.emby] [backends.emby.servers] [backends.emby.servers.server1] url = "http://192.168.1.99:8920" weight = 1 [frontends.emby] backend = "emby" passHostHeader = true [frontends.emby.headers] SSLRedirect = true ForceSTSHeader = true STSSeconds = 315360000 BrowserXssFilter = true FrameDeny = true ContentTypeNosniff = true [frontends.emby.routes] [frontends.emby.routes.route1] rule = "Host:emby.mydomain.net" navigating to http://emby.mydomain.net yields a bad gateway error....can anyone help?
makarai 109 Posted January 19, 2019 Posted January 19, 2019 I have since moved Emby Server off of docker and into my local linux host on 192.168.1.99. Since I have the rest of my media apps running in a docker host though, using traefik as a reverse proxy they are all accessible via https://app.domain.com (using Let's Encrypt certs) What I would like to do is still reverse proxy emby server using a separate rules.toml file, which I have successfully done for FreeNAS, Unifi, and Ubuntu VM. [backends.emby] [backends.emby.servers] [backends.emby.servers.server1] url = "http://192.168.1.99:8920" weight = 1 [frontends.emby] backend = "emby" passHostHeader = true [frontends.emby.headers] SSLRedirect = true ForceSTSHeader = true STSSeconds = 315360000 BrowserXssFilter = true FrameDeny = true ContentTypeNosniff = true [frontends.emby.routes] [frontends.emby.routes.route1] rule = "Host:emby.mydomain.net" navigating to http://emby.mydomain.net yields a bad gateway error....can anyone help? Not sure about traeffic reverse proxy, but i did a lot with nginx as well as ha proxy. I suppose traffic is offloading ssl, if so you should point your backend server to your http port 8096, or if you have on the lan side of things ssl encryption, you should point it to url = "https://192.168.1.99:8920"
bigverm23 2 Posted January 19, 2019 Author Posted January 19, 2019 @@makarai modified to [backends.emby] [backends.emby.servers] [backends.emby.servers.server1] url = "https://192.168.1.99:8920" weight = 1 still bad gateway, wonder if there is something i need to change in Advanced settings in emby server
makarai 109 Posted January 19, 2019 Posted January 19, 2019 (edited) @@makarai modified to [backends.emby] [backends.emby.servers] [backends.emby.servers.server1] url = "https://192.168.1.99:8920" weight = 1 still bad gateway, wonder if there is something i need to change in Advanced settings in emby server Often, a reverse proxy takes over the ssl entpoint. So give url = "http://192.168.1.99:8096" a try If its just a forward, so to speak, you have to add the ssl cert to emby with the advanced settings Edited January 19, 2019 by makarai
bigverm23 2 Posted January 19, 2019 Author Posted January 19, 2019 What should I be setting if anything ine emby settings
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