If you want to run multiple ProtonVPN connections simultaneously on a UniFi Dream Machine (UDM) router or any other UniFi gateway, you’ll quickly encounter a problem:
All generated WireGuard configuration files from ProtonVPN use the same internal IP address. As a result, only one VPN connection can be active at a time – all others will fail.
In this article, you’ll learn why this happens and how to fix it easily by changing just one line in your WireGuard configuration.
The Problem: Identical IP Addresses in WireGuard Configs
When you generate several WireGuard profiles from ProtonVPN (for example, for different countries or servers), they all contain the same IP address in the [Interface] section.
Example:
[Interface]
# Key for ProtonVPN-DE
# Bouncing = 15
# NetShield = 1
# Moderate NAT = on
# NAT-PMP (Port Forwarding) = off
# VPN Accelerator = on
PrivateKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Address = 10.2.0.2/32
DNS = 10.2.0.1
[Peer]
# DE#501
PublicKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = 194.126.177.8:51820
If you now create another profile (e.g., for Albania or any other location), it will look almost identical – including the same IP address 10.2.0.2/32.
The Cause: ProtonVPN Doesn’t Assign Unique IPs Per Profile
When ProtonVPN generates WireGuard configuration files, it assigns the same internal client address for your account each time.
This isn’t usually a problem if you connect only one device.
However, if you want to establish multiple VPN tunnels through a UniFi router (for example, for different VLANs, routing rules, or countries), each connection needs a unique internal address.
The Fix: Manually Change the IP Address
The solution is simple:
In each ProtonVPN WireGuard configuration file, edit the Address = ... line and increment the second number after the 10.
This allows multiple connections to coexist without conflicts.
Example:
First VPN Config (Germany)
[Interface]
Address = 10.2.0.2/32
DNS = 10.2.0.1
Second VPN Config (Albania)
[Interface]
Address = 10.3.0.2/32
DNS = 10.2.0.1
Third VPN Config (Switzerland)
[Interface]
Address = 10.4.0.2/32
DNS = 10.2.0.1
πΉ Important:
Only change theAddressline in the[Interface]section.
Do not modify the PrivateKey, DNS, or Endpoint settings.
Setup on UniFi (UDM / UDM-Pro / UDR)
- Enable WireGuard:
WireGuard is supported natively on UniFi devices (UDM/UDR) in newer firmware versions, or can be enabled via UDM-Tools. - Create a VPN Client:
In the UniFi Network interface, go toSettings β Teleport & VPN β VPN Clients β Create New VPN Client. - Import the WireGuard File:
Choose file upload and import your modified ProtonVPN configuration. - Add a Second VPN Client:
Repeat the process using your next modified config (e.g., the one withAddress = 10.3.0.2/32). - Optional – Configure Routing:
You can now use routing rules or VLANs to decide which traffic goes through which VPN tunnel.
Advantages of This Method
β
Run multiple VPN tunnels at the same time
β
No more IP conflicts between ProtonVPN connections
β
Simple fix without touching ProtonVPN server configs
β
Works on UniFi UDM, UDM-Pro, UDR, and UXG routers
Conclusion
ProtonVPN officially assigns only one WireGuard IP per account, but with a UniFi router setup, you can easily work around this limitation by manually adjusting the internal address.
This allows you to use multiple VPN clients simultaneously – perfect if you want different VLANs or locations routed through different ProtonVPN servers.
In short:
Just change
Address = 10.2.0.2/32to10.3.0.2/32,10.4.0.2/32, and so on – and your UniFi router can handle multiple ProtonVPN connections at the same time.
Hi, Iβm a trained IT specialist in system integration and have been working as a Linux system administrator for several years. At home, I feel most comfortable with Proxmox, Ubuntu, and Debian β these three accompany me both at work and on my personal servers. When Iβm not busy at the shell, I enjoy tinkering with new projects, testing exciting open-source tools, or optimizing existing setups. On linuxbase.io, I want to share my experiences so others donβt have to stumble over the same pitfalls.
