Related GitHub issue #1246
This list has been provided on the Discord by Pantii
- Protocol "Wireguard TCP" is selected (other protocols gave me problems)
- no custom DNS configured (if i put in custom dns and point to PM adress, i get conflicts)
- Killswitch can be activated, but only the Basic one, not "advanced"
- when using SPN, exclude all ProtonVPN apps/profiles from it
(so far no split tunneling and excluding PM is needed)
- Open the Proton VPN Application
- Open settings, go to the Connections tab, enable "Custom DNS Servers"
- Input
127.0.0.1 as your DNS Server to loopback to Portmaster
Optional:
4. Select the Advanced tab and look for "Split-Tunneling"
5. Exclude C:\ProgramData\Safing\Portmaster\Portmaster-start.exe
When excluding Portmaster-start.exe from Split-Tunneling you loose the ability to use Killswitch.
- Open Portmaster UI
- Select ProtonVPN.exe
- Disable Block Secure DNS Bypassing
- Open Windows Settings
- Select "Network & internet"
- Click on "Ethernet"
- Scroll down to "DNS server assignment"
- Change from "Automatic" to "Manual" and toggle on IPv4
- Enter the DNS adress:
127.0.0.1
- There is a few methods but we'll be using the terminal
- Edit
/etc/systemd/resolved.conf with your favorite editor
- Locate the DNS lines and uncomment the line by removing the hash (
#) symbol.
- Enter the DNS address as follows:
DNS=127.0.0.1
- Open
Services.msc
- Search for Portmaster Core (
PortmasterCore)
- Change Startup type from
Automatic to Automatic (Delayed Start)
- Proton VPN requires tweaking to work after Proton VPN version 3.*
- Wireguard can be hit or miss.