June 10Jun 10 Dear fellow Unraiders,When I set up a ProtonVPN Wireguard Config through the Unraid VPN Settings and assign it to a docker container (like Brave, but I tried multiple browsers from different Repos) I get a connection and when I check with whatsmyip the correct IP of the proton Server is shown. When I check with DNS Leak though, I see the Gateway Address of my ISP. I tried forcing the Container to use the provided DNS server (from Proton) with the --dns flag but then I don't get any DNS at all.My Unraid server is behind a pfSense firewall, and since I have a DSlite connection my IPv4 traffic goes through my ISPs AFTR Gateway by default in pfSense. Is it just not possible to use the Proton DNS servers with this setup or am I missing something? Oh and I turned Secure DNS off in Brave of course :) Thanks a ton for your help!Best,Lukas
June 17Jun 17 Author No one here running Unraid behind pfSense and has an idea where I could start to look for the problem? :/
June 17Jun 17 9 hours ago, Luvide said:No one here running Unraid behind pfSense and has an idea where I could start to look for the problem? :/What Dns are you using in the settings? I use surfshark and have to use their dns servers
June 17Jun 17 Author Do you mean Unraid Settings or pfSense? In Unraid the main DNS server is my firewall since I want the VPN connection to only apply to Docker Containers. If you mean the VPN DNS Settings then yes, I tried using the proton dns servers from the wireguard config, but I still get the above mentioned result from an apparent dns leak
June 17Jun 17 Yes, I meant the dns in the unraid settings. It has been a while since I set it up, but it did take a bit to get it right. I see you're not the only one who has had this issue.Have you seen this?Wireguard DNS leaks with ProtonVPN - General Support - Unraid
June 17Jun 17 Author yeah, I saw this. Adding the route mentioned in the post changed nothing and the --dns flag prevents the container from having any dns resolution.this is my vpn config:
June 17Jun 17 Community Expert docker extra parm option may be worth a try.--dns 8.8.8.8https://docs.docker.com/engine/network/#dns-services
June 18Jun 18 Community Expert I do mine a little different. Have you tried using pfsense to setup an OpenVPN path? With that in place, you can assign your containers IP addresses and route through whichever gateway you want.
June 19Jun 19 Author well, using the extra parm doesn't work, I get DNS Probe possible errors. I'll try to set it up on pfSense itself when I find the time soon - I unfortunately also had problems getting a connection (well, it connected but would load incredibly slowly) to both pangolin and netbird (both using their modified wireguard solutions) so I'm thinking maybe something is wrong with my firewall configuration (even though everything else works nicely and tailscale has no problems at all)..
June 19Jun 19 Author one of their support people told me after some bugfixing it was probably some weird unraid networking thing, but until now I wasn't able to find anything and the problems just keep piling up :/
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.