So I have been going quite a bit crazy trying to figure out how to run Prowlarr and SABnzbd behind Traefik whilst having them run behind Gluetun. I try for a bit and then get sick of trying to figure out where I have gone wrong and leave it for a while, I give it a crack again, fail and then leave it. The cycle repeats. I would love some assistance on how I can get this (If i can get this) to run properly. I asked ChatGPT and it solved a couple of small issues but i just couldn’t get it working.
The Traefik logs are saying “unable to get IP address from container” and i presurme being the 2 services are labelled to service:gluetun this could be the issue. When i placed it under the Traefik network it still couldn’t find IP or work. I added the address to the SABnzbd whitelist and traefik is registering the connections are all good. Im totally at a loss here. I feel like im missing a traefik label to make this work.
Any assistance would be greatly appreciated
version: "3"
services:
gluetun:
image: qmcgaw/gluetun:latest
container_name: gluetun
network_mode: "traefik"
environment:
- TZ=Canada/Pacific
- PUID=1000
- PGID=1000
- VPN_SERVICE_PROVIDER=protonvpn
- OPENVPN_USER=xxxxxxxx
- OPENVPN_PASSWORD=xxxxxxxx
- SERVER_COUNTRIES=Canada
- FIREWALL_OUTBOUND_SUBNETS=192.168.0.1/24
volumes:
- /srv/dev-disk-by-uuid-5b41b37b-0f2f-b67a-ff6cb0bfdda0/Configs/Gluetun:/gluetun
labels:
#SABnzbd
traefik.enable: true
traefik.http.routers.sabnzbd.entryPoints: https
traefik.http.routers.sabnzbd.rule: Host(\sabnzbd.domain.com`)`
traefik.http.routers.sabnzbd.service: sabnzbd
traefik.http.services.sabnzbd.loadbalancer.server.port: 8084
#Prowlarr
traefik.http.routers.prowlarr.entryPoints: https
traefik.http.routers.prowlarr.rule: Host(\prowlarr.domain.com`)`
traefik.http.routers.prowlarr.service: prowlarr
traefik.http.services.prowlarr.loadbalancer.server.port: 9696
ports:
- 8084:8080 #SABnzbd
- 9696:9696 #Prowlarr
- 8000:8000 #API
cap_add:
- NET_ADMIN
restart: unless-stopped
sabnzbd:
image: linuxserver/sabnzbd:latest
container_name: sabnzbd
network_mode: "service:gluetun"
environment:
- PUID=1000
- PGID=1000
- TZ=Canada/Pacific
volumes:
- /srv/dev-disk-by-uuid-5b41b37b-b67a-ff6cb0bfdda0/Configs/SABnzbd:/config
- /srv/dev-disk-by-uuid-5b41b37b2f-b67a-ff6cb0bfdda0/Media:/Media
labels:
flame.type: application
flame.name: SABnzbd
flame.url: http://192.168.0.1:8084
flame.icon: https://cdn.jsdelivr.net/gh/walkxcode/dashboard-icons@master/png/sabnzbd-alt.png
depends_on:
- gluetun
restart: unless-stopped
prowlarr:
image: linuxserver/prowlarr:latest
container_name: prowlarr
network_mode: "service:gluetun"
environment:
- PUID=1000
- PGID=1000
- TZ=Canada/Pacific
volumes:
- /srv/dev-disk-by-uuid-5b41b37b-04367a-ff6cb0bfdda0/Configs/Prowlarr:/config
labels:
flame.type: application
flame.name: Prowlarr
flame.url: http://192.168.0.1:9696
flame.icon: https://cdn.jsdelivr.net/gh/walkxcode/dashboard-icons@master/png/prowlarr.png
depends_on:
- gluetun
restart: unless-stopped
Is there a reason why you want prowlarr and sab behind a VPN in the first place? If you just turn on TLS in sabnzbd you’re not going to run into any issues and it’s probably a better idea to search with prowlarr through your home address depending on what trackers you’re using. I don’t have either of these behind a VPN for my setup personally.
Gluetun just needs to share a docker network with traefik and not use network_mode. Do you have a default network in this compose file? If not you should add the same network name to every container and test to see if you can reach prowlarr with
docker exec traefik wget -O - http://gluetun:9696.Gluetun with protonvpn disconnects constantly for me and requires dependent containers to restart when it reconnects (https://github.com/qdm12/gluetun/issues/641) so make sure if you’re testing stuff they’re all restarted together