Sonarr reverse proxy2/28/2023 I have another container running ( amule) in a setup like sonarr (so with network_mode: 'service:transmission' and depends_on: transmission). This is a "fix" but there is a way to solve without creating many nginx containers? I don't have only sonarr but also other services behind the transmission-openvpn.Ġ 11:49:46 31#31: *199 open() "/etc/nginx/html/login" failed (2: No such file or directory), client: 192.168.0.50, server:, request: "GET /login?returnUrl=/sonarr HTTP/1.1", host: "X.X.X.X:9090"ġ92.168.88.50 - garret "GET /login?returnUrl=/sonarr HTTP/1.1" 404 153 "-" "Mozilla/5.0 (Windows NT 10.0 Win64 圆4 rv:87.0) Gecko/20100101 Firefox/87.0"Ġ 11:49:46 31#31: *199 open() "/etc/nginx/html/favicon.ico" failed (2: No such file or directory), client: 192.168.0.50, server:, request: "GET /favicon.ico HTTP/1.1", host: ""X.X.X.X:9090", referrer: " 192.168.88.50 - garret "GET /favicon.ico HTTP/1.1" 404 153 " "Mozilla/5.0 (Windows NT 10.0 Win64 圆4 rv:87.0) Gecko/20100101 Firefox/87.0"Īt the same time I notice that the address in the address bar changes to (and to recap I get a 404 not found error page). Do you know why and how to fix it?ĮDIT 2: It seems that the only way to solve is to create a second transmission-proxy container but this one is linked to the sonarr container( links: sonarr:sonarr). Can you help me understanding what I am doing wrong?ĮDIT: Ok I just realized that I should use for the reverse proxy but I get a 404 Not Found error when accessing that address. I am able to access transmission through the 9091 port but I am not able to see Sonarr (on port 8989). Proxy_set_header X-Forwarded-Proto $scheme Proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for Proxy_pass proxy_set_header Host $http_host
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |