Replies: 4 comments 3 replies
-
|
Did anyone ever get to the bottom of this? As far as I can tell I have tried subnets with no chance of overlap and it seems to make no difference. V3 stable and latest v3.39.1 act identically Enabling debug logging does not make anything jump out to me other than this looks like the command being issued is either malformed or not correct in context but there is not enough logging detail to know precisely what that command is and since it shutdowns immediately after I cant debug the normal shell into container way. |
Beta Was this translation helpful? Give feedback.
-
|
Have you found a solution to this? (Asking since this was initially brought up over a year ago) |
Beta Was this translation helpful? Give feedback.
-
|
This works for me now. Coincidentally I tried again last week and using the same approach it just operates as documented. |
Beta Was this translation helpful? Give feedback.
-
|
Funnily enough, I just got my setup working too |
Beta Was this translation helpful? Give feedback.
-
|
This appears to be an issue again. After adding FIREWALL_OUTBOUND_SUBNETS environmental variable gluetun fails to start. Any workaround or help would be greatly appreciated. I'm using the latest tag as of now |
Beta Was this translation helpful? Give feedback.
-
|
for me FIREWALL_OUTBOUND_SUBNETS seems to be doing nothing docker exec -it gluetun ip route that was my value, doing this fixes the issue manually docker exec -it gluetun ip route add 192.168.100.0/24 via 192.168.0.1 dev eth0 any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
had a similar issue, try FIREWALL_OUTBOUND_SUBNETS=10.0.0.0/24, the .1 gave me invalid argument |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I had all my services in a single docker compose and worked fine. However Radarr was not working correctly with IMDB and radarr support says it's related to using a VPN and not to put it behind VPN. So I've put gluetun into a separate docker compose stack and am attaching only certain dockers to it.
Gluetun runs normally and makes a VPN connection.
However to allow non-vpn dockers outside the stack to access I have added - FIREWALL_OUTBOUND_SUBNETS=10.0.0.1/24
(all other dockers are on a custom macvlan network with individual IP addressed on this subnet. The host machine for docker/portainer is also on the same subnet).
When I add this line it exits with error:
ERROR adding outbound subnet to routes: adding route for subnet 10.0.0.1/24: replacing route for subnet 10.0.0.1/24 at interface eth0: invalid argument
INFO Shutdown successful
Here is my gluetun docker compose:
`
version: "3"
services:
gluetun:
container_name: gluetun
image: qmcgaw/gluetun
networks:
LAN:
ipv4_address: 10.0.0.224
devices:
- /dev/net/tun
ports:
- 9117:9117/tcp #jackett
- 8181:8181/tcp #sabnzbd
- 9696:9696/tcp #prowlarr
- 8112:8112/tcp #deluge
- 56673:56673/tcp #deluge
- 56673:56673/udp #deluge
- 8085:8085/tcp #qbittorrent
- 49710:49710/tcp #qbittorrent
- 49710:49710/udp #qbittorrent
- 3000:3000/tcp #firefox
- 3001:3001/tcp #firefox
- 5800:5800/tcp #myjdownloader
- 5800:5800/udp #myjdownloader
cap_add:
- NET_ADMIN
environment:
- VPN_SERVICE_PROVIDER=airvpn
- VPN_TYPE=wireguard
- WIREGUARD_PRIVATE_KEY=redacted=
- WIREGUARD_PRESHARED_KEY=redacted=
- WIREGUARD_ADDRESSES=redacted
- SERVER_COUNTRIES=redacted
- FIREWALL_VPN_INPUT_PORTS=redacted
- FIREWALL_OUTBOUND_SUBNETS=10.0.0.1/24 # added this to get access to LAN from container
networks:
LAN:
external: true
`
Beta Was this translation helpful? Give feedback.
All reactions