Open maurocolella opened 1 year ago
I was having the same issue and solved it by moving the Traefik labels to the vpn container & also adding the network you use for Traefik to the vpn container under the networks
property. e.g.
nordvpn:
image: azinchen/nordvpn:latest
container_name: vpn2
networks:
- {your network name}
cap_add:
...
labels:
- "traefik.enable=true"
- "traefik.http.routers.qbittorrent.rule=Host(`qbittorrent.nas.home`)"
- "traefik.http.services.qbittorrent.loadbalancer.server.port=7000"
- "traefik.docker.network=nordvpn-2_default"
I believe this will route the outbound traffic through the vpn, but still allow Traefik to route inbound web traffic through the vpn to the correct container, assuming you have the correct ports open on the vpn.
Thanks a lot gwest
for the explanation, this seems to be it. It's also more of a general configuration matter with Traefik in this scenario, ie. containers need to be on the same network.
Hi.
This is fantastic, but I am unable to access the qbittorrent web ui using a traefik subdomain.