If you haven't set the default route manually in NetworkManager it must be pushed by the server. So please post the server configuration and the clients routing table.

Same with me or like i did. Deleting it solved ALL the problems there were with the gateways, the ifconfig problems and everything else. In a second :(

Thanks, this was a really helpful hint as I had exactly the same problem with openSUSE Tumbleweed!

@dad311: Ive successfully setup OpenVPN remote access and PIA OpenVPN client.  Both work, but both dont work at the same time. If I have the PIA cleint enable, remote OpenVPN clients will not connect.  I believe the issue is remote access traffice is coming in the WAN interface and going out the PIA interface. Anyone know how to force my Openvpn server to use the only WAN interface?? thx Have you by any chance found any solution? I suspect there is a Firewall rule conflicting between the 2 interfaces/instances of OpenVPN - the PIA side (client) and the OpenVPN server which we inetnd to use to connect to our home network form a remote address.

@viragomann: I don't know about latency issues in 2.4.1 and trouble to install the Client Export package in 2.3.4. However, you can export certs separately if you want. The Client Export tool only bundles config, certs and Windows installer. But why want you use WinSCP? Just use the GUI: System > Certificate Manager > Certificates Thank you very much for your answer. I ended up updating and installing the Export Tool. I'm just hoping I won't have any issues with speeds now…

firewall > rules > lan add the ip of the devices to the list, then under the settings change the gateway to WAN_dhcp. this is how i allow netflix to play on my TV while the rest of the network is under PIA VPN

Thanks viragomann!

Shared key can only have one client per server. You would have to switch to an SSL/TLS setup to have multiple clients on a single server.

It depends on why it stopped. If it fails because of an auth error at PIA, then OpenVPN considers that fatal and exits. We have a fix for that on 2.4.1 and later (using "auth-retry nointeract") If there is something else causing it to exit, then the fix would be different. Have to see the error in the OpenVPN logs to know for sure. If the process is exiting, then using the Service Watchdog package to monitor it will help treat the symptom, but not cure the original problem.

Ok, so I finally figured it out. OMG. I had created a cert with a type-o in it and the verify-x509-name was erroring when I tried to connect to machines that were on the domain. That's why some worked and some didn't, because some were on the domain and some weren't. Once I got that all fixed up everything else was easy. Thanks so much for taking the time to look at this with me.

I am using UDP, currently I have disabled the vpn and am using the windows client. Would really like to use pfsense as I have more than one machine that I would like to vpn. As I said above if anyone needs any more info just ask.

I'd probably put a route to the server in the openvpn client side and a route to the client subnet on the server side…  However, I'm not super genius, so may not work.

I've got this working, in case someone else stumbles on this and has issues my problem was that the username didn't match the certificate name. Andy

Damn I totally forgot to add rules on the only interface firewall that I had to let users use that OpenVPN like I have done with 53 port from DNS Resolver. Thanks anyway.

Thanks for the info. I have done as suggested & posted to the OpenVPN forum.

I should qualify this, it only happens when I am connected to the web page via OpenVPN. Is his normal? The OpenVPN Connection I am attempting to kill is not my web connection, but a separate router