I don’t understand why Proton can’t generate WireGuard configs with IPV6 from their downloads page. I found this: https://gist.github.com/mikaeldui/12127c91ccece42ea375c9f42d94aa8a to manually edit the WireGuard configs but it is a lot of steps.

IPv6 is the way to go for the future, especially considering that IPv6 is more secured with some of its underlying encrypted protocols and faster performance.

Furthermore, since my mobile carrier blocks all IPv4 traffic, I cannot use an eSIM on my phone with ProtonVPN.

I need to emphasize the importance of IPv6 support when connecting to ProtonVPN.

I am running a Home Assistant instance in my local network with an open port through DSLite - Only IPv6 is unique to my network, hence Home Assistant is only accessible through its IPv6 address.
It is critical for me and my fiance to be able to connect through ProtonVPN to our Home Assistant network when we're out and about, outside the range of our local network.
In addition, running the Home Assistant instance through ProtonVPN would yield even greater security.

It is 2024, and it is simply a must from a security point of view. I can understand IPv6 not being supported for free users, but paying customers should have access to current technology, flexibility and security.

When connecting through Wireguard using a config file (with AllowedIPs adjusted for ipv6), you gain access to the IPv6 internet for a few moments after setting the interface up (server NL-323095 2a02:6ea0:c041:2317::14 and server US-207060 2a02:6ea0:c803:3092::13 from ip.me; ipv6.google.com reachable). This suggests the infrastructure is probably ready for it. I'm going to report this as a bug, and we'll see what they say.

UPDATE: Netherlands server gives me a stable IPv6 connection. US server still drops ipv6 after a few moments.

UPDATE 2: I got a reply from them. IPv6 support is still experimental, but some servers are already providing it. Users of the free servers can help test it: https://www.reddit.com/r/ProtonVPN/comments/zf5b79/were_testing_ipv6_on_our_servers_and_we_need_your/

Enabling users to use this feature as an IPV6 gateway similar how you allow access to TOR through VPN would be a rockstar move.

Good to see it "planned" now!

This is a must, I understand the problem about ipv6 over ProtonMail, it's almost hardcore task to filter spam or massmailing, but in the VPN, I was offered a disccount to work without ipv4 on my current ISP, and Ix now facing the stupidity over the top, routing wireshark traffic to one of a VPS server, from the phone and iptables routing that traffic to ipv4 IPs like proton or duckduckgo, it's a neccesary bad, nowdays whatever reason could explain the lack of IPv6 routes to a VPN provider, more even not providing both a ipv4 and ipv6 exit ip, that's its 101 in any dedicated server. Make half of the new servers added every month only IPv6 your provider prolly went cheaper on those backbones.

It's almost 2024 now and IPv6 Support is still missing... It's fairly simple to implement, at least for OpenVPN on Linux.

I want to connect with IPv6 endpoints, because IPv6 is often lighter when IPv4 is too busy and the line is slow.

I am switching more of my services over to IPV6 and can't use some of them because I am running through Proton VPN. Please support IPV6.

How is this even missing in 2022... +everyvote I have

SInce IPv6 is more and more common with consumer grade ISP, it would really be great. At least for the wireguard servers since it's really straight forward to do it if the servers already have an IPv6 address. in this case we just need to add the address and route ::0 in the wireguard configuration