NordVPN doesn't reconnect after routine periodic VPN server maintenance or other issues...
-
NordVPN (openvpn) runs great under pfSense 2.6.0; however, approximately every 7 to 10 days, I lose internet connection due to routine VPN server maintenance. pfSense will show both WAN and NordVPN running when in reality OpenVPN is actually down due to routine maintenance or other NordVPN issues. pfSense doesn't reflect its true status and never reconnects automatically when the system has been restored. 
I was under the impression that "Gateway Monitoring Daemon" is designed to keep services active. It seems useless to me.
Initially, my suspicion was the cable modem, Netgear. I thought it was on its way out. After numerous calls to Comcast, the cable modem was ruled out as the culprit. I even had a Comcast technician come to the house to test the system. Everything checked out okay. Now, instead of unplugging the cable modem every time the internet goes down, I just refresh "OpenVPN client: NordVPN" under service status, this method quickly restores OpenVPN. I wish there was an option in pfsense {server list} for multiple VPN servers that the system would automatically refresh or switch the VPN server when it is down for maintenance or due to other issues. The current setup causes problems because you only have the option for one VPN server at a time in openvpn because when it goes down, you have to manually change to a new server or keep refreshing the current server. Is there a way to configure pfSense to make this process automatic or have it auto switch to a different VPN server? Am I doing something wrong? Your help would be greatly appreciated, thanks!
-
@ghost-0 said in NordVPN doesn't reconnect after routine periodic VPN server maintenance or other issues...:
Am I doing something wrong?
Calling the Comcast technician when your VPN service isn't working is wrong.
Other than that, no.
It is not that comfortable running vpn services on pfSense. Worst thing, often different clients get the same address and gateway and don't work anymore but pfSense doesn't care.
