search

navilg / media-stack

A stack of self-hosted tools to manage and stream media. Sonarr + Radarr + qBitTorrent + Prowlarr + Jellyfin + Jellyseerr + VPN
MIT License
516 stars 83 forks source link

Fixing Prowlarr via VPN #13

Closed RobinFlikkema closed 1 year ago

RobinFlikkema commented 1 year ago

This is a fix for the error mentioned on commit bf1cd779310ff4e119a1a4e1b6c4a1b793e501ce

Error response from daemon: conflicting options: port publishing and the container type network mode

RobinFlikkema commented 1 year ago

Excuse me if I'm overlooking something. But this fix seems to work.

I commented the ports out so people could use that when not using VPN. But I'm unsure if this is the way to go since I'm only running profile 2.

@bakersomo, this should fix your issue also since this is the fix you mentioned :)

EDIT: It seems that inter container networking changes due to this (of course). But it should be possible; just requires more work: https://github.com/qdm12/gluetun/wiki/Inter-containers-networking

wdfrench13 commented 1 year ago

I got the gluetun container/mullvad VPN/prowlarr setup working this weekend using this PR and info from the link you shared, @RobinFlikkema

One key bit that took me a bit to find: you need to add an outbound firewall rule to the gluetun container to talk to the secondary docker network, like so: - FIREWALL_OUTBOUND_SUBNETS=172.18.0.0/24 as shown in this answer

Your work here was very helpful, thanks!

navilg commented 1 year ago

Thanks @RobinFlikkema I surely missed to add those ports in main branch.

navilg commented 1 year ago

One key bit that took me a bit to find: you need to add an outbound firewall rule to the gluetun container to talk to the secondary docker network, like so: - FIREWALL_OUTBOUND_SUBNETS=172.18.0.0/24 as shown in this answer

is it required when VPN container is running in different network than other stacks? I am not sure about this issue. Here we have considered all the containers (including vpn) in same network.

RobinFlikkema commented 1 year ago

I got the gluetun container/mullvad VPN/prowlarr setup working this weekend using this PR and info from the link you shared, @RobinFlikkema

One key bit that took me a bit to find: you need to add an outbound firewall rule to the gluetun container to talk to the secondary docker network, like so: - FIREWALL_OUTBOUND_SUBNETS=172.18.0.0/24 as shown in this answer

Your work here was very helpful, thanks!

Unsure. I just assigned static IPs to the containers and then it all seems to work.