Proton doesn’t allow website access on my work WiFi, but a free VPN does

Site Feedback
1

TL;DR ProtonVPN doesn’t allow website access on my work WiFi, but a free VPN does.

Hello, I’m a new customer. I bought 2 years of ProtonVPN a couple days ago during the Black Friday sale.

I had used Mullvad intermittently over the last few years as well as a free option called VPN Proxy Master since unsubscribing to Mullvad.

Well I’m at work today and I try to open Reddit but it doesn’t load. I am on my own personal laptop and my own personal phone, with no higher-up administrative control on these devices other than the WiFi I am connected to.

I connect to the fastest/closest VPN server near me with no results. I try a bunch of different servers on different settings in different countries. Still doesn’t work. I try other sites that my work has blocked and I also don’t have access.

Then I switch to cellular data and redownload the free VPN I used to use. After connecting, everything works.

The reason I bought Proton VPN Plus was because I didn’t feel safe/secure on the free option of the aforementioned service.

Maybe there’s a blacklist of VPNs in the company’s WiFi settings and Proton is on the list.

Is there any workaround for the obstacles I faced today or should I just refund?

Any advice or response is appreciated, thanks.

2

On the off chance that only certain protocols are blocked, you could try switching between the available protocols in your client to see if it makes a difference in being able to connect: https://protonvpn.com/support/how-to-change-vpn-protocols (e.g. try Stealth protocol).

3

Does your phone have hotspot capability? If so, perhaps you could connect your laptop through your phone to see if Proton VPN will work in that configuration. That should eliminate a possible conflict between Proton VPN and your employer’s WiFi. Just a thought . . .

4

Looks like someone just made a post about this 3 hours ago. My apologies

5

Thank you for the reply. I’ll give this a try

6

That’s a clever workaround. I ended up solving it by playing around with the protocol settings like the support team recommended. I’m sure your comment will help someone in the future with a similar problem though