![]() ![]() Sonarr will now prefix every request to both ports with the provided Base-URL so we can make it work with a Reverse Proxy. I've also confirmed using curl -4 from within the containers that the traffic is indeed being routed through the vpn.įor each additional service you want to add, you simply add an additional server stanza, changing the ports to those required by your service. The default ‘ SSL Port Number ‘ isn’t relevant as Sonarr/Radarr will be listening on both ports. For this example that would be 192.168.1.XXX:9091 for transmission or 192.168.1.XXX:8989 for sonarr. Glad I managed to get it work and hopefully don't have to touch it more.ĭoing it this way means you don't need to alter any URLBase values and allows your services to be accessed as normal - as if there isn't a proxy running at all. I usually like to deep down things but this reverse proxy thing seems so obscure to me. This log file contains fatal, error, warn, and info entries. ![]() The current log file is always radarr.txt, for the the other files radarr.0.txt is the next newest (the higher the number the older it is) up to 51 log files total. I did the same for other services and the reverse proxy works in this way. Radarr uses rolling log files limited to 1MB each. The issue was as I had already figured out above that in sonarr I have to setup such urlbase to /sonar/. Hope there is an easy fix to solve this by doing something on the nf file.ĮDIT 2: I think I resolved. But it is also missing one crucial point. Then I saw Overseerr whith ticks many boxes: The good arr - like userinterface and name. I was hoping there was a cleaner way to achieve my end goal.ĮDIT: I noticed that if I set the in urlbase settings of sonarr the field /sonarr/, then the reverse proxy works when I access Now I have to figure out how to change somehow this urlbase in such containers where I cannot directly change it. Before stumbling upon this project, ombi practically was a given besides its small downfall using proxy for requests. The issue is that I have 6 containers "linked" to transmission-openvpn and thus it would mean to create 6 more nginx containers. Thus, it seems to depend on the type container maybe? The ones from linuxserver (sonarr, jackett, bazarr, etc.) don't work at all for instance.Īgain, the only way to solve seems to create a proxy container for each of my container that shares the same network with transmission-openvpn. If I go to I can see the login page and everything works but just the images of the webpages are not loaded. 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 I'm on windows 10, running the latest version of Sonarr.Proxy_pass proxy_set_header Host $http_host I've been trying to troubleshoot this myself for days with no luck and no ideas of where else to look. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |