Deluge leaking IP on ipleak.net ?

[needsupport]

Is this urgent?

None

Host OS

Debian bookworm

CPU arch

x86_64

VPN service provider

Custom

What are you using to run the container

Portainer

What is the version of Gluetun

v3.39.0

What's the problem 🤔

Deluge is leaking my real IP address. It is running with network set to container mode with gluetun :
I used ipleak.net to check my IP and torrent IP leaks
I did not bind to anything since gluetun should ideally not leak my VPS real IP address since all connections for deluge are through the gluetun container

Share your logs (at least 10 lines)

|       ├── Interface addresses:
|       |   └── 10.13.37.22/24
|       ├── Allowed IPs:
|       |   ├── 0.0.0.0/0
|       |   └── ::/0
|       └── Network interface: tun0
|           └── MTU: 1400
├── DNS settings:
|   ├── Keep existing nameserver(s): no
|   ├── DNS server address to use: XXXX
|   └── DNS over TLS settings:
|       ├── Enabled: yes
|       ├── Update period: every 24h0m0s
|       ├── Unbound settings:
|       |   ├── Authoritative servers:
|       |   |   └── cloudflare
|       |   ├── Caching: yes
|       |   ├── IPv6: no
|       |   ├── Verbosity level: 1
|       |   ├── Verbosity details level: 0
|       |   ├── Validation log level: 0
|       |   ├── System user: root
|       |   └── Allowed networks:
|       |       ├── 0.0.0.0/0
|       |       └── ::/0
|       └── DNS filtering settings:
|           ├── Block malicious: yes
|           ├── Block ads: no
|           ├── Block surveillance: no
|           └── Blocked IP networks:
|               ├── 127.0.0.1/8
|               ├── 10.0.0.0/8
|               ├── 172.16.0.0/12
|               ├── 192.168.0.0/16
|               ├── 169.254.0.0/16
|               ├── ::1/128
|               ├── fc00::/7
|               ├── fe80::/10
|               ├── ::ffff:127.0.0.1/104
|               ├── ::ffff:10.0.0.0/104
|               ├── ::ffff:169.254.0.0/112
|               ├── ::ffff:172.16.0.0/108
|               └── ::ffff:192.168.0.0/112
├── Firewall settings:
|   ├── Enabled: yes
|   └── VPN input ports:
|       └── 6881
├── Log settings:
|   └── Log level: info
├── Health settings:
|   ├── Server listening address: 127.0.0.1:9999
|   ├── Target address: cloudflare.com:443
|   ├── Duration to wait after success: 5s
|   ├── Read header timeout: 100ms
|   ├── Read timeout: 500ms
|   └── VPN wait durations:
|       ├── Initial duration: 6s
|       └── Additional duration: 5s
├── Shadowsocks server settings:
|   └── Enabled: no
├── HTTP proxy settings:
|   ├── Enabled: yes
|   ├── Listening address: :8888
|   ├── User: 
|   ├── Password: [not set]
|   ├── Stealth mode: yes
|   ├── Log: no
|   ├── Read header timeout: 1s
|   └── Read timeout: 3s
├── Control server settings:
|   ├── Listening address: :8000
|   └── Logging: yes
├── OS Alpine settings:
|   ├── Process UID: 1000
|   └── Process GID: 1000
├── Public IP settings:
|   ├── Fetching: every 12h0m0s
|   ├── IP file path: /tmp/gluetun/ip
|   └── Public IP data API: ipinfo
└── Version settings:
    └── Enabled: yes
2024-09-04T06:32:22Z WARN DNS address is set to 95.215.19.53 so the DNS over TLS (DoT) server will not be used. The default value changed to 127.0.0.1 so it uses the internal DoT serves. If the DoT server fails to start, the IPv4 address of the first plaintext DNS server corresponding to the first DoT provider chosen is used.
2024-09-04T06:32:22Z INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.2 and family v4
2024-09-04T06:32:22Z INFO [routing] adding route for 0.0.0.0/0
2024-09-04T06:32:22Z INFO [firewall] setting allowed subnets...
2024-09-04T06:32:22Z INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.2 and family v4
2024-09-04T06:32:22Z INFO TUN device is not available: open /dev/net/tun: no such file or directory; creating it...
2024-09-04T06:32:22Z INFO [dns] using plaintext DNS at address XXXXX
2024-09-04T06:32:22Z INFO [http proxy] listening on :8888
2024-09-04T06:32:22Z INFO [http server] http server listening on [::]:8000
2024-09-04T06:32:22Z INFO [firewall] allowing VPN connection...
2024-09-04T06:32:22Z INFO [healthcheck] listening on 127.0.0.1:9999
2024-09-04T06:32:22Z INFO [wireguard] Using available kernelspace implementation
2024-09-04T06:32:22Z INFO [wireguard] Connecting to XXXX:51820
2024-09-04T06:32:22Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
2024-09-04T06:32:22Z INFO [healthcheck] healthy!
2024-09-04T06:32:22Z INFO [firewall] setting allowed input port 6881 through interface tun0...
2024-09-04T06:32:22Z INFO [dns] downloading DNS over TLS cryptographic files
2024-09-04T06:32:24Z INFO [dns] downloading hostnames and IP block lists

Share your configuration

No response

[github-actions]

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[qdm12]

Deluge is leaking my real IP address. It is running with network set to container mode with gluetun :
I used ipleak.net to check my IP and torrent IP leaks

I'm also using Deluge. Check on the bottom right of the web ui, you'll see your public IP address. Is it your VPN ip address or not? Double check at https://ipinfo.io

I also tried going to ipleak.net and using the Torrent Address detection but the torrent won't work with the errors "Error: skipping tracker announce (unreachable)" and "Error: timed out" 🤷

[Pelvis99]

#2484 might be related