You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.
I just checked the IPs my Torrent Setup is leaking to the outside and was shocked finding out that my VPN IP AND my real IP are leaking through. I used this Tool: (ipleak.net)
Current setup
information about your current setup
docker image tag (ex: python, latest, 32242d1 ...)
python
docker image hash (ex: 603b78e07727)
f696e56e6591
docker-compose.yml file or docker run command
how did you start the container? (don't forget to use backticks for creating a proper code block)
A simple fix is to prevent qbit using different network interface than tun1. Had this before with qbit and protonvpn on my main machine and without docker. Seems to be a config problem from qbit.
A simple fix is to prevent qbit using different network interface than tun1. Had this before with qbit and protonvpn on my main machine and without docker. Seems to be a config problem from qbit.
Information
I just checked the IPs my Torrent Setup is leaking to the outside and was shocked finding out that my VPN IP AND my real IP are leaking through. I used this Tool: (ipleak.net)
Current setup
information about your current setup
python
,latest
,32242d1
...)603b78e07727
)docker-compose.yml
file ordocker run
commandhow did you start the container? (don't forget to use backticks for creating a proper code block)
The text was updated successfully, but these errors were encountered: