Proton VPN doesn't work while portmaster is on

[atacanelifakman-lgtm]

What worked?

Turning off portmaster, quite littirally shuting it down, dont know how much more detailed it gets lol

What did not work?

turning off all filters, reseting VPN (multible times), setting DNS on Wi-Fi (i was desparate ok?), changing the encription method on Proton VPN, etc.

Additional information

it's like a 50/50 chance which will shaite the bed first to be honest, "dont know what the heck is going on under the hood but i dont like the sound the engines making" is the only way i can describe it tbh

Debug-Info: https://support.safing.io/privatebin/?35d04e339ef40bfa#Hs7shGLMohJEkeqDTBnqkaY2VBzaVjHAmCMwrMFYCoaZ

[github-actions[bot]]

Hey @atacanelifakman-lgtm, thank you for reporting on a compatibility.

We keep a list of compatible software and user provided guides for improving compatibility in the wiki - please have a look there. If you can't find your software in the list, then a good starting point is our guide on How do I make software compatible with Portmaster.

If you have managed to establish compatibility with an application, please share your findings here. This will greatly help other users encountering the same issues.

[github-actions[bot]]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[atacanelifakman-lgtm]

re-tested WireGuard to make sure, it does NOT work with Proton VPN Ver. 4.3.1 it seem's, welp, guess i have to choose one of the two now lol

[atacanelifakman-lgtm]

and yes, ive tried to trubleshoot it, everything green, still doesnt work (no internet on the VPN according to windows) and stains the bed after like 5-10 minutes.

[LogicalError007]

I am facing same issues.

[stenya]

Just for your information: We’ve received reports from some users experiencing a similar issue after the latest Proton VPN updates. Reverting to the previous version (Proton v4.2.0) has resolved the problem for them.

[LogicalError007]

It's not the same app but WSL started having this problem when I tried to connect it to the internet for updating.

This has happened before with both WSL and Proton VPN. Have to shutdown Portmaster to make these apps work.

[cod3nym]

Hey so I just figured out how to resolve this:

ProtonVPN has apparently introduced a new feature for DNS blocking using NPRT. Disabling that feature and using the normal DNS blocking mode fixes the internet connection issues.

(I also have my DNS in ProtonVPN set to 127.0.0.1 as described in Portmasters compatibility guide)

[wistb]

having the same issue as op with proton vpn 4.3.4 and portmaster 2.0.25. I've followed the compatibility guide. @cod3nym 's workaround doesn't appear to be available on this version

[reweb0]

I'm using ProtonVPN version 4.3.5 and, like @wistb I don't find dns block handling.

[ellartdev]

I managed to make it work on v4.3.5 by checking "Access devices by name" Box in ProtonVPN client's Settings -> Advanced settings.

• Custom DNS servers: 127.0.0.1
• Protocol: Smart
• Kill Switch: Basic

[wistb]

I managed to make it work on v4.3.5 by checking "Access devices by name" Box in ProtonVPN client's Settings -> Advanced settings.

• Custom DNS servers: 127.0.0.1
• Protocol: Smart
• Kill Switch: Basic

this works, thanks! vpn v4.3.5 portmaster 2.0.25

[reweb0]

@wistb @ellartdev It's working for me under Linux while using WireGuard because the Linux client doesn't have Smart protocol. It's not working wile using OpenVPN.

I'm using ProtonVPN version 4.3.5 and, like @wistb I don't find dns block handling.

In my previous post, I was under Windows, but I didn't have time to test under Windows yet. I'll test very soon and keep you informed guys.

[eabase]

Also check #1246. And try this:

# Run in admin powershell
sc config "PortmasterCore" depend= "ProtonVPN WireGuard" start= delayed-auto

[Mascarponi3]

I managed to make it work on v4.3.5 by checking "Access devices by name" Box in ProtonVPN client's Settings -> Advanced settings.

• Custom DNS servers: 127.0.0.1
• Protocol: Smart
• Kill Switch: Basic

this works, thanks! vpn v4.3.5 portmaster 2.0.25

This setup was working for me too. However, since ProtonVPN updated to v4.3.7 is doesn't anymore.

There are 3 ProtonVPN services running in Portmaster (ProtonVPN.client.exe, ProtonVPNService.exe,ProtonVPN.WireGuardService.exe). I unblocked all.

In ProtonVPN I use/used these settings:

Custom DNS servers: 127.0.0.1 Protocol: Smart Kill Switch: Basic Acces device by name Nat-type 3

Anybody better results combining these 2 ?

[eabase]

@Mascarponi3

Where did you find that quoted text? It seem that you need to file a bug issue to ProtonVPN team. And mention it on their Reddit page.

There are 3 ProtonVPN services ... I unblocked all.

AFAICT, it's not about unblocking, it's about making sure they all start before Portmaster. Setting up the VPN performs all sorts of complex handshakes, so anything blocked or delayed there, may break it.

But then again Proton does something different than most other VPN providers, which is probably also why it seem to work better at other times.

[Mascarponi3]

The quoted text was from this post. And in my case it's not about starting ProtonVPN before Portmaster, in all kinds of different ways starting both programs, they don't work together anymore in the last version (4.3.9).

I downgraded back to 4.3.5 a week ago, which worked fine again, but although i unchecked 'automatic updates' recently the Proton app updated itself to 4.3.9, and again the problem occured.