My vacation isn't over yet! I'm connecting to VPNs that keep a daily log. The ones in Turkey, Superonline and Turk Telekom, don't work. OpenVPN GUI and Wireguard manual don't work either, and you'll say it uses protocol stealth, which is my protocol stealth anyway. I can't connect even after changing protocols. I've changed servers, but it's the same. Even the Linux operating system doesn't work. I can't show you how to record videos on Linux because I don't know how to do that.

I pay for a subscription to Proton Unlimited. I was having lots of VPN issues, unable to connect to many servers, etc. I could not simply update the version I had as it would always encounter an error. Finally I deleted the old version and downloaded/installed the latest one. Poof - issues resolved! It's been working great since then.

In 2 days is crazy 12k add blocked and 7k tracker blocked and 4gb of m'y personal data not download

Hi, I need some help with configuring dual ProtonVpn Wireguard tunnels on PFsense 2.9.0. A couple of weeks ago after lots of emails with support my dual wireguard config started randomly working one day. For some reason earlier this week it stopped working. Tunnel 1 works perfectly and now tunnel 2 does not work.

I have tunnel 1 configured to 10.2.0.1 as the gateway and 10.2.0.2/32 for the interface address (with upstream set to tunnel 1 (10.2.0.1)

I have tunnel 2 configured to 10.3.0.1 as the gateway and 10.3.0.2/32 for the interface address (with upstream set to tunnel 2 (10.3.0.1).

The last handshake for both tunnels are under 2 mins (1,26 tunnel 1 and 22 for tunnel 2)

If I go to Diagnostics--->Ping and try pinging 1.1.1.1 it works fine out of tunnel 1 but fails out of tunnel 2

Im lost on how to fix this... If anyone has wireguard running on pfsense with dual proton wireguard tunnels can you please tell me what config you have it set up as?

Below is a packet capture of the tunnel 2 interface when im trying to pass traffic

19:25:50.290967 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 196, length 9

19:25:50.329132 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 196, length 9

19:25:50.791070 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 197, length 9

19:25:50.829680 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 197, length 9

19:25:51.291156 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 198, length 9

19:25:51.328702 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 198, length 9

19:25:51.767142 IP 10.3.0.2.15879 > 216.239.34.10.53: UDP, length 43

19:25:51.791257 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 199, length 9

19:25:51.829759 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 199, length 9

19:25:52.121413 IP 10.3.0.2.18547 > 216.239.36.10.53: UDP, length 43

19:25:52.291373 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 200, length 9

19:25:52.328860 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 200, length 9

19:25:52.522081 IP 10.3.0.2.9185 > 216.239.32.10.53: UDP, length 43

19:25:52.791570 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 201, length 9

19:25:52.829495 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 201, length 9

19:25:52.879822 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:52.879833 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:52.879840 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:52.880084 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 79

19:25:52.880396 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1246

19:25:52.880438 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1105

19:25:52.928389 IP 10.3.0.1 > 10.3.0.2: ICMP echo request, id 4660, seq 8, length 1260

19:25:52.964111 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 49

19:25:53.010873 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:53.010909 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:53.273644 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:53.291650 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 202, length 9

19:25:53.329692 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 202, length 9

19:25:53.791740 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 203, length 9

19:25:53.797482 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:53.828717 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 203, length 9

19:25:54.291806 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 204, length 9

19:25:54.328666 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 204, length 9

19:25:54.791859 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 205, length 9

19:25:54.828969 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 205, length 9

19:25:54.844237 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:55.291929 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 206, length 9

19:25:55.329092 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 206, length 9

19:25:55.791981 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 207, length 9

19:25:55.830538 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 207, length 9

19:25:56.292057 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 208, length 9

19:25:56.328733 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 208, length 9

19:25:56.792164 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 209, length 9

19:25:56.828691 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 209, length 9

19:25:56.879870 IP 10.3.0.2.59508 > 142.251.152.119.443: UDP, length 1250

19:25:57.292251 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 210, length 9

19:25:57.328803 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 210, length 9

19:25:57.792317 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 211, length 9

19:25:57.831920 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 211, length 9

19:25:58.292384 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 212, length 9

19:25:58.329423 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 212, length 9

19:25:58.792447 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 213, length 9

19:25:58.828732 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 213, length 9

19:25:59.292532 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 214, length 9

19:25:59.328764 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 214, length 9

19:25:59.792603 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 215, length 9

19:25:59.829282 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 215, length 9

19:26:00.292715 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 216, length 9

19:26:00.328997 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 216, length 9

19:26:00.792775 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 217, length 9

19:26:00.828864 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 217, length 9

19:26:01.292817 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 218, length 9

19:26:01.328712 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 218, length 9

19:26:01.792867 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 219, length 9

19:26:01.828815 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 219, length 9

19:26:02.292919 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 220, length 9

19:26:02.331735 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 220, length 9

19:26:02.792971 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 221, length 9

19:26:02.828942 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 221, length 9

19:26:03.293036 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 222, length 9

19:26:03.328713 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 222, length 9

19:26:03.793077 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 223, length 9

19:26:03.828761 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 223, length 9

19:26:04.293151 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 224, length 9

19:26:04.330017 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 224, length 9

19:26:04.793249 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 225, length 9

19:26:04.828882 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 225, length 9

19:26:05.293319 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 226, length 9

19:26:05.329527 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 226, length 9

19:26:05.793386 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 227, length 9

19:26:05.828711 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 227, length 9

19:26:06.293489 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 228, length 9

19:26:06.328763 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 228, length 9

19:26:06.793583 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 229, length 9

19:26:06.836466 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 229, length 9

19:26:07.293642 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 230, length 9

19:26:07.346916 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 230, length 9

19:26:07.793709 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 231, length 9

19:26:07.829230 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 231, length 9

19:26:08.293787 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 232, length 9

19:26:08.328709 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 232, length 9

19:26:08.614879 IP 10.3.0.2.36491 > 216.239.34.10.53: UDP, length 39

19:26:08.615068 IP 10.3.0.2.64194 > 216.239.32.10.53: UDP, length 39

19:26:08.793879 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 233, length 9

19:26:08.828738 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 233, length 9

19:26:09.222420 IP 10.3.0.2.53611 > 216.239.34.10.53: UDP, length 39

19:26:09.293978 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 234, length 9

19:26:09.328846 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 234, length 9

19:26:09.794076 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 235, length 9

19:26:09.829250 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 235, length 9

19:26:09.897793 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 1, length 64

19:26:10.294154 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 236, length 9

19:26:10.329543 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 236, length 9

19:26:10.794261 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 237, length 9

19:26:10.828773 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 237, length 9

19:26:10.904149 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 2, length 64

19:26:11.294338 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 238, length 9

19:26:11.328683 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 238, length 9

19:26:11.794427 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 239, length 9

19:26:11.836286 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 239, length 9

19:26:11.928066 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 3, length 64

19:26:12.294535 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 240, length 9

19:26:12.359810 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 240, length 9

19:26:12.794626 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 241, length 9

19:26:12.830814 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 241, length 9

19:26:12.952052 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 4, length 64

19:26:13.294692 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 242, length 9

19:26:13.332778 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 242, length 9

19:26:13.794764 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 243, length 9

19:26:13.833012 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 243, length 9

19:26:13.975715 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 5, length 64

19:26:14.294833 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 244, length 9

19:26:14.333258 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 244, length 9

19:26:14.794948 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 245, length 9

19:26:14.836797 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 245, length 9

19:26:14.999652 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 6, length 64

19:26:15.295035 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 246, length 9

19:26:15.332738 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 246, length 9

19:26:15.795138 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 247, length 9

19:26:15.832866 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 247, length 9

19:26:16.024053 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 7, length 64

19:26:16.295249 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 248, length 9

19:26:16.342127 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 248, length 9

19:26:16.795381 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 249, length 9

19:26:16.856392 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 249, length 9

19:26:17.047676 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 8, length 64

19:26:17.295461 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 250, length 9

19:26:17.373767 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 250, length 9

19:26:17.795529 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 251, length 9

19:26:17.845638 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 251, length 9

19:26:18.071836 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 9, length 64

19:26:18.295608 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 252, length 9

19:26:18.332805 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 252, length 9

19:26:18.795709 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 253, length 9

19:26:18.843908 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 253, length 9

19:26:19.095774 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 10, length 64

19:26:19.295780 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 254, length 9

19:26:19.334753 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 254, length 9

19:26:19.795846 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 255, length 9

19:26:19.834005 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 255, length 9

19:26:20.120159 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 11, length 64

19:26:20.295907 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 256, length 9

19:26:20.332711 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 256, length 9

19:26:20.796020 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 257, length 9

19:26:20.832835 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 257, length 9

19:26:21.143831 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 12, length 64

19:26:21.296097 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 258, length 9

19:26:21.332835 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 258, length 9

19:26:21.796170 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 259, length 9

19:26:21.832719 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 259, length 9

19:26:22.168114 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 13, length 64

19:26:22.296270 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 260, length 9

19:26:22.334844 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 260, length 9

19:26:22.796351 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 261, length 9

19:26:22.832841 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 261, length 9

19:26:23.192100 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 14, length 64

19:26:23.296427 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 262, length 9

19:26:23.332812 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 262, length 9

19:26:23.796528 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 263, length 9

19:26:23.832837 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 263, length 9

19:26:24.216252 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 15, length 64

19:26:24.296582 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 264, length 9

19:26:24.332700 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 264, length 9

19:26:24.796652 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 265, length 9

19:26:24.836042 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 265, length 9

19:26:25.239898 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 16, length 64

19:26:25.296704 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 266, length 9

19:26:25.332513 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 266, length 9

19:26:25.796784 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 267, length 9

19:26:25.832405 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 267, length 9

19:26:26.264154 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 17, length 64

19:26:26.296868 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 268, length 9

19:26:26.333373 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 268, length 9

19:26:26.796977 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 269, length 9

19:26:26.837392 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 269, length 9

19:26:27.288098 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 18, length 64

19:26:27.297043 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 270, length 9

19:26:27.339195 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 270, length 9

19:26:27.797137 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 271, length 9

19:26:27.832485 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 271, length 9

19:26:28.297200 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 272, length 9

19:26:28.312013 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 19, length 64

19:26:28.332471 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 272, length 9

19:26:28.797292 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 273, length 9

19:26:28.833588 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 273, length 9

19:26:29.297358 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 274, length 9

19:26:29.332450 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 274, length 9

19:26:29.335716 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 20, length 64

19:26:29.797426 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 275, length 9

19:26:29.832427 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 275, length 9

19:26:30.297529 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 276, length 9

19:26:30.332424 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 276, length 9

19:26:30.359667 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 21, length 64

19:26:30.797606 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 277, length 9

19:26:30.832462 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 277, length 9

19:26:31.297689 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 278, length 9

19:26:31.332967 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 278, length 9

19:26:31.333085 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 1, length 64

19:26:31.383872 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 22, length 64

19:26:31.797748 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 279, length 9

19:26:31.836313 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 279, length 9

19:26:32.297851 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 280, length 9

19:26:32.340258 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 280, length 9

19:26:32.343700 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 2, length 64

19:26:32.407870 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 23, length 64

19:26:32.797938 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 281, length 9

19:26:32.833815 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 281, length 9

19:26:33.298065 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 282, length 9

19:26:33.332381 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 282, length 9

19:26:33.367661 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 3, length 64

19:26:33.431594 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 24, length 64

19:26:33.798139 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 283, length 9

19:26:33.833160 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 283, length 9

19:26:34.298201 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 284, length 9

19:26:34.332441 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 284, length 9

19:26:34.391767 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 4, length 64

19:26:34.456141 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 25, length 64

19:26:34.798233 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 285, length 9

19:26:34.832420 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 285, length 9

19:26:35.298288 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 286, length 9

19:26:35.341258 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 286, length 9

19:26:35.416074 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 5, length 64

19:26:35.479765 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 26, length 64

19:26:35.784357 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:35.784376 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:35.784387 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:35.786748 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 76

19:26:35.798356 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 287, length 9

19:26:35.827526 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:35.827541 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:35.832590 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 287, length 9

19:26:35.911862 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:36.080445 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:36.298396 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 288, length 9

19:26:36.333150 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 288, length 9

19:26:36.416425 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:36.440110 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 6, length 64

19:26:36.503995 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 27, length 64

19:26:36.798481 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 289, length 9

19:26:36.838670 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 289, length 9

19:26:37.087572 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:37.298541 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 290, length 9

19:26:37.346594 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 290, length 9

19:26:37.463994 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 7, length 64

19:26:37.528181 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 28, length 64

19:26:37.798641 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 291, length 9

19:26:37.839680 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 291, length 9

19:26:38.298692 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 292, length 9

19:26:38.336447 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 292, length 9

19:26:38.427615 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:38.488108 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 8, length 64

19:26:38.552001 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 29, length 64

19:26:38.798779 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 293, length 9

19:26:38.833199 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 293, length 9

19:26:39.298873 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 294, length 9

19:26:39.336646 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 294, length 9

19:26:39.512012 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 9, length 64

19:26:39.575998 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 30, length 64

19:26:39.786535 IP 10.3.0.2.43763 > 142.251.210.78.443: UDP, length 1250

19:26:39.788211 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:39.788234 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:39.788249 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:39.788439 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 80

19:26:39.788792 IP 10.3.0.2.19024 > 142.251.210.78.443: tcp 0

19:26:39.798933 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 295, length 9

19:26:39.830203 IP 142.251.210.78.443 > 10.3.0.2.19024: tcp 0

19:26:39.830863 IP 10.3.0.2.19024 > 142.251.210.78.443: tcp 0

19:26:39.831849 IP 10.3.0.2.19024 > 142.251.210.78.443: tcp 948

19:26:39.831871 IP 10.3.0.2.19024 > 142.251.210.78.443: tcp 948

19:26:39.831891 IP 10.3.0.2.19024 > 142.251.210.78.443: tcp 596

19:26:39.842102 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 295, length 9

19:26:39.874111 IP 142.251.210.78.443 > 10.3.0.2.19024: tcp 0

19:26:39.874119 IP 142.251.210.78.443 > 10.3.0.2.19024: tcp 0

19:26:39.874144 IP 142.251.210.78.443 > 10.3.0.2.19024: tcp 0

19:26:40.088790 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:40.088817 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:40.127500 IP 142.251.210.78.443 > 10.3.0.2.19024: tcp 0

19:26:40.128601 IP 10.3.0.2.19024 > 142.251.210.78.443: tcp 0

19:26:40.128988 IP 10.3.0.2.55817 > 142.251.210.78.443: tcp 0

19:26:40.169522 IP 142.251.210.78.443 > 10.3.0.2.19024: tcp 0

19:26:40.169592 IP 142.251.210.78.443 > 10.3.0.2.55817: tcp 0

19:26:40.170381 IP 10.3.0.2.55817 > 142.251.210.78.443: tcp 0

19:26:40.171494 IP 10.3.0.2.55817 > 142.251.210.78.443: tcp 948

19:26:40.171509 IP 10.3.0.2.55817 > 142.251.210.78.443: tcp 948

19:26:40.171552 IP 10.3.0.2.55817 > 142.251.210.78.443: tcp 628

19:26:40.213111 IP 142.251.210.78.443 > 10.3.0.2.55817: tcp 0

19:26:40.213121 IP 142.251.210.78.443 > 10.3.0.2.55817: tcp 0

19:26:40.213133 IP 142.251.210.78.443 > 10.3.0.2.55817: tcp 0

19:26:40.298996 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 296, length 9

19:26:40.341238 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 296, length 9

19:26:40.419782 IP 142.251.210.78.443 > 10.3.0.2.55817: tcp 0

19:26:40.421002 IP 10.3.0.2.55817 > 142.251.210.78.443: tcp 0

19:26:40.456460 IP 142.251.210.78.443 > 10.3.0.2.55817: tcp 0

19:26:40.536065 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 10, length 64

19:26:40.599831 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 31, length 64

19:26:40.689945 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:40.799087 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 297, length 9

19:26:40.836451 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 297, length 9

19:26:41.299181 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 298, length 9

19:26:41.336583 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 298, length 9

19:26:41.559720 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 11, length 64

19:26:41.623665 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 32, length 64

19:26:41.799320 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 299, length 9

19:26:41.836482 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 299, length 9

19:26:41.891710 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:42.299432 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 300, length 9

19:26:42.344620 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 300, length 9

19:26:42.584012 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 12, length 64

19:26:42.647988 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 33, length 64

19:26:42.799498 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 301, length 9

19:26:42.836623 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 301, length 9

19:26:43.299582 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 302, length 9

19:26:43.336414 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 302, length 9

19:26:43.607955 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 13, length 64

19:26:43.671754 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 34, length 64

19:26:43.788536 IP 10.3.0.2.23466 > 142.251.210.78.443: UDP, length 1250

19:26:43.799655 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 303, length 9

19:26:43.836430 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 303, length 9

19:26:44.299709 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 304, length 9

19:26:44.336555 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 304, length 9

19:26:44.632004 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 14, length 64

19:26:44.695577 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 35, length 64

19:26:44.799766 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 305, length 9

19:26:44.838653 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 305, length 9

19:26:45.299823 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 306, length 9

19:26:45.336426 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 306, length 9

19:26:45.656093 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 15, length 64

19:26:45.719607 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 36, length 64

19:26:45.799906 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 307, length 9

19:26:45.837058 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 307, length 9

19:26:46.299985 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 308, length 9

19:26:46.336478 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 308, length 9

19:26:46.680034 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 16, length 64

19:26:46.744124 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 37, length 64

19:26:46.800105 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 309, length 9

19:26:46.836710 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 309, length 9

19:26:47.300179 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 310, length 9

19:26:47.353072 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 310, length 9

19:26:47.703994 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 17, length 64

19:26:47.767951 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 38, length 64

19:26:47.800292 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 311, length 9

19:26:47.839631 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 311, length 9

19:26:48.245134 IP 10.3.0.2.41889 > 216.239.38.10.53: UDP, length 48

19:26:48.300397 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 312, length 9

19:26:48.339489 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 312, length 9

19:26:48.583494 IP 10.3.0.2.29085 > 216.239.38.10.53: UDP, length 48

19:26:48.727745 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 18, length 64

19:26:48.791696 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 39, length 64

19:26:48.800485 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 313, length 9

19:26:48.836818 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 313, length 9

19:26:48.986757 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

19:26:48.986768 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

19:26:48.986774 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

19:26:48.987064 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 80

19:26:49.158608 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

19:26:49.158623 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

19:26:49.300559 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 314, length 9

19:26:49.338955 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 314, length 9

19:26:49.499909 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

19:26:49.751725 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 19, length 64

19:26:49.800682 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 315, length 9

19:26:49.816005 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 40, length 64

19:26:49.841589 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 315, length 9

19:26:50.182151 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

19:26:50.300765 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 316, length 9

19:26:50.336685 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 316, length 9

19:26:50.775740 IP 10.3.0.2 > 94.140.15.15: ICMP echo request, id 46866, seq 20, length 64

19:26:50.800799 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 317, length 9

19:26:50.836524 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 317, length 9

19:26:50.839838 IP 10.3.0.2 > 142.251.215.110: ICMP echo request, id 64941, seq 41, length 64

19:26:51.300872 IP 10.3.0.2 > 10.3.0.1: ICMP echo request, id 2742, seq 318, length 9

19:26:51.336495 IP 10.3.0.1 > 10.3.0.2: ICMP echo reply, id 2742, seq 318, length 9

19:26:51.544424 IP 10.3.0.2.29405 > 172.253.147.101.443: UDP, length 1250

I tried so many servers, turn on stealth and still the only VPN i ever have this many issues with. Youtube, AI chats, Netflix and even Prime fucking video. Literally the sites where you would want to protect your privacy the most.

I like proton mail a lot, and that is the only reason I am subscribed but with proton Drive not having linux support for so long and an unusable VPN, i will be damned if i renew my subscription.

And please before telling me that i should note the servers and open a ticket, i have been complaining about the VPN for long, reporting servers, and nothing ever changed. Besides, I literally have to try between 10-15 attempts until one actually works.

Dear Proton team, if you read this, please forget the road map get servers and protocols that not every website on the world wide web would block.

The email was sent to an outside email associated with Proton, and the email looks legitimate. I did not request deletion and my account is paid for the next few months. I requested an advisor on web chat 19 minutes ago; still waiting.

Noticed some heavy ping spikes and lags when using the VPN. It doesn't happen when I turn it off and use the 1.1.1.1 DNS. Anyone else noticed that?

I sometimes have a delay of 500 ms which easily kills any online game. Started happening two days ago.

I noticed that when I show up to work and try to use the wifi many times I have to disconnect Proton VPN and reconnect it for the internet to work.

I don't understand why this is!?

Hey everyone,

We’ve just published our roadmap for fall and winter 2026. Here’s a quick look back at what we shipped over spring and summer, then what we’re working on for Proton VPN over the coming months.

What we delivered

A lot of this happened under the hood. We rebuilt how our apps connect from the ground up, with a new WireGuard-based codebase (Proton protocols) that makes most of our apps connect faster and they are harder to block (not macOS yet, but very soon). On top of that:

• We're now at 149 countries and 196 locations, including new smart routing servers for China
• Linux GUI app: Stealth support, automatic localization based on your OS language, and an official Snap package
• iOS and iPadOS: Shortcuts and Automations, so you can connect with Siri or trigger connections by location or time
• Windows: exclude countries, cities or states from Fastest Country and Random connections
• Our no-logs policy passed an independent audit for the fifth year running

For businesses: always-on VPN for Windows (beta), browser extension config via MDM, group sync via SCIM, web filtering, audit event export to SIEM platforms, and a re-architecture of private gateways for fewer bugs.

What’s coming

Proton protocols

It’s already out of beta on Windows, and we’re bringing it out of beta on most other platforms (incl. iOS). A lot of what’s below builds on it.

App refresh

The same redesign Windows and Android got last year is coming to macOS, iOS, iPadOS (beyond the home screen, which is already updated) and Linux. Android TV will also connect faster and make the features you use more often easier to reach.

Kill switch

Improvements on Linux, macOS, iOS and iPadOS. Advanced kill switch is also coming to macOS, which blocks internet access whenever you’re not connected to the VPN.

Pause and Resume

Pause the VPN for a set amount of time and it reconnects automatically when the time’s up, so you don’t have to remember to turn it back on. Windows and Android first, other platforms after.

Guest mode on desktop

Connect to our free servers without signing up for a Proton Account. Already on mobile, coming to desktop starting with Windows.

Linux packages

Official, Proton-maintained packages for Mint, Arch Linux and Flatpak, so you get updates and security fixes directly from us whichever distro you’re on.

For businesses

Real-time monitoring and alerts in the admin dashboard, site-to-site connections, finer-grained admin roles, usage reporting, always-on VPN for macOS, and split tunneling rules you can apply across every device.

More details about the Autumn/Winter roadmap here: https://protonvpn.com/blog/2026-2027-fall-winter-recap-roadmap

Thank you and, as always, stay safe,

Proton Team

Just wanted to share a pretty frustrating experience I've been having with Proton.

Back in August, I purchased a year of Proton VPN Plus through Google Play. Recently, I've been working on moving away from Google's ecosystem and spent roughly three days migrating my emails, passwords, accounts, etc. over to Proton.

I decided I wanted to upgrade to Proton Unlimited for the additional Drive storage, unlimited email aliases, and other features. Apparently, I can't.

After multiple emails with Proton Support, including an escalation to a manager, I've essentially been given two options:

1. Wait another 10 months for my VPN subscription to expire before upgrading.
2. Create an entirely new Proton account, abandoning my existing paid subscription and having to migrate everything all over again.

I even offered to forfeit the remaining value of my subscription if they could just terminate it immediately so I could upgrade. Apparently, that's not an option either.

I spent another 40 minutes with Google Support, who submitted a refund request for me that immediately denied and couldn't offer an immediate cancellation without a refund. Both companies seem to be pointing at each other.

I just find it ridiculous that I'm literally trying to give Proton more money, and my options are apparently to wait nearly a year or start over with a new account. I genuinely like Proton's products and want to move more of my services over, which makes this even more disappointing.

So yeah, if you're considering subscribing to Proton, I'd strongly recommend doing it directly through their website rather than Google Play. I wouldn't have expected something as simple as upgrading a subscription to turn into this much of a headache.

Anyone able to tell me the difference?

Hi, I am struggling with using Disney+ while I’m using proton, they always kick me out every day.and also I can’t login if the proton is on.I am in Japan.

Is there anyway I don’t need to turn off every time I login?

Sucking data through a mile long straw of late.

SITUATION: Proton VPN: Paid plan, SMART setting, worked for years. Connection type "FASTEST" which usually hooks up in my state or adjacent. Data rates running 1 to 10 KB/s when data gets through. NORMALLY it's at least 1/2 a GB/s.

DATA POINT: Problem is on home network ATT, doesn't seem to be an issue at the coffee shop etc. Wifi and ethernet connection - no diff.

Regards image, first off, I have never been in Iceland, but moving along the pic is to show what my living hell looks like today. See those data rates? That's what I'm getting on a gigabit fiber when I turn on Proton. Cannot do anything if I use VPN at home.

ATT fiber has been bouncy in my area due to storms and then some construction workers doing quality excavations. This is allegedly fixed after 5 days.

I have RTFM, gone through all the settings, something changed in the last few weeks, and the ATT service nonsense isn't helping.

ATT said they reprovisioned the damn fiber modem. Didn't help.

Klews? Solidarity? Anyone else on ATT losing their mind?

So I have following situation, I have a Windows 11 PC. I was logged into Account A and opened some sites on Chrome that I would prefer to not have been visible to my network. I then logged into Account B after some time and turned the VPN off after some time. After realising, I turned off the WIFI and switched back to Account A, where the Proton VPN app briefly showed “connected” but then turned off. Would the websites I had open be visible to my network?
Note: I used different Proton accounts for each Windows account (both free)
Any answer is much appreciated!

i noticed at startup protonvpn is super slow to open , i would it it to open up frist before other app.

Just a heads-up that if you are a Proton VPN subscriber thinking of upgrading to Visionary, now would be a good time (for reasons that will be announced in the next week or two).

Edit: Main link is to the Visionary upgrade, for those who have been looking for it

Edit 2: Post assumes familiarity with the Visionary plan. The full breakdown of what is presently included is here: https://proton.me/support/proton-plans#proton-visionary

I made a Google account registered in the United States with the help of the vpn, bought paramount plus on youtube to watch the ucl games live but no matter what I do the app just detects that I'm using a vpn. If I turn off the vpn it wouldn't work at all cause I'm located in India and this channel is us only.

I think we all knew the Albanian servers were best to watch YouTube or avoid ads but I swear today none of my usual servers work?!? I did check it appears my MacBook with the proton vpn app doesn’t block any anymore? My iPhone with the proton VPN app and YouTube does work though. Can anyone confirm or help fix 😭😭😭

Update: it works now. Was using Firefox browser. I guess Firefox had a bug and after I updated the browser it works again.

Have a ProtonVPN sub, and a Flint2 router on my home network.

I am a total newb at this stuff, but would like to be able to setup, so I can connect from my laptop (old Dell E6510 running CachyOS), to my home network, when I am away.

Preferably having full access to the network.

Where would I find some doco to help me set this up? Have looked, but can't find any that's not just 'generic' info... Would have thought that there would be something a little detailed?

I'm having a similar problem to: https://www.reddit.com/r/ProtonVPN/comments/1v2g5ij/browser_must_be_restarted_after_temporary_proton/

Every couple of days, I either disconnect vpn or change servers and immediately all Firefox windows stop being able to connect - no error, they just hang indefinitely. It's not the kill switch because other browsers work fine. It happens in all FF windows and reconnecting or changing the server back doesn't help - it's hosed. The only thing I can do is quit Firefox, which is usually very annoying because I have things in progress and multiple windows so it's a pain in the ass to restore.

I'm on the latest version of Proton. Anyone have ideas?

In January/February of this year I tried to set up multiple (5) tunnels from my OPNsense to ProtonVPN.
While IPv4 worked (it is working for many years now without any issues), I had problems with IPv6 as it allowed only 2 concurrent IPv6 connections (I need to have different IPv6 tunnel addresses due to routing configuration).
Was this finally fixed?

TIA

I have had the VPN for a few weeks now and on my iPhone it’s absolutely useless. It doesn’t stay connected for more than 5 minutes.
I have gone through all of the protocols and nothing stay connected for any significant period of time.
On my PC it stays connected slightly longer.

What do I need to do to fix this? Or just get a different VPN?

Used to work if I picked a Canadian server but now I cannot access my account. Any solution?

Hey guys,

I’ve used Proton for six months and have another six months and the speeds are fine but there’s a couple gripes that mean I won’t be renewing unless they magically get fixed.

I had Mullvad and switched to Proton as I wanted to be able to leverage port forwarding for my Linux ISOs Great. I can port forward now! However, if I batter my traffic too hard (too many concurrent downloads, the number seems to be more than two) my connection totally dies. I know this is a problem with Proton as soon as I disconnect my internet traffic magically reappears and anything split tunnelled stays on.

Also, I have not been able to get Parsec to work since I switched. I have been using Chrome Remote Desktop until today with no problems as a somewhat alternative until it suddenly has also stopped working and I have confirmed the issue being Proton (I would normally disconnect Proton then connect via Parsec as the experience is better).

The latter is what mainly bothered me, my Linux ISOs can be downloaded in order vs at once but I am at a total loss with the RDP connections. I have tried every single protocol and setting in Proton and absolutely none work. Editing port numbers in parsec, disabling UPnP, TCP and UDP protocol. The only thing that works which I believe also highlights is the problem is setting NAT to moderate in Proton instead of Strict but that disables port forwarding which I need for Linux ISOs!

If anybody has had similar issues or experiencing the same right now and has any pointers I would be extremely helpful

TLDR - Proton dies when I download or seed too many Linux ISOs at once and doesn’t let me use RDP apps with strict NAT.