Pritunl Single Host behind an Elastic or Network Load Balancer - Clients occasionally cannot route

Pritunl Pritunl VPN
1

I had a setup consisting of two hosts sitting behind an AWS NLB, where the OpenVPN connection is running on each host.

I had a few users reporting inconsistent connectivity issues - where they were connected but could not reach anything on the VPC.

I thought it was something to do with having two hosts, as when I narrowed it down to one host, the problem seemed to go away, however today it happened again with a user on the single host having to disconnect and reconnect.

Do you have any advice on where to check and what to look at given these symptoms?

I did have the port open so that the two hosts could talk to each other, and I have the setting for behind a loadbalancer enabled, but the issue seems to persist.

Thank you in advance!

2

I had a problem that sound a bid like that not sure if it is the same, try and disable “VXLan Routing” if it is enabled and do some testing.

3

Network load balancing shouldn’t be used unless needed. The client will already automatically handle connecting to multiple hosts and failover to another host if one is offline. The network load balancer will create issues for some authentication configurations that require web requests to be sent to the server. This includes the dynamic firewall, single sign-on connection authentication and all WireGuard connections.