@jknott said in OpenVPN Not working after update: Are there changes in the new version (again) that cause earlier versions to fail? There are always some pesky minor changes, that's why "just updating" pfSense == updating OpenVPN creates "OpenVPN Not working after update". The "OpenVPN server" is just a process that listens on a port, typically UDP/1194. That's just a firewall rule, no nat needed. When the connection doesn't work, that is because the 'client' doesn't understand the 'server', or the other way around.

@gertjan That setting doesn't work for me in the issue I've been having.

I also have encountered this issue. What occurs is that pfSense sometimes gloms the options together when OpenVPN is restarted, causing a syntax error. So pull-filter ignore "ifconfig-ipv6" pull-filter ignore "route-ipv6" becomes pull-filter ignore "ifconfig-ipv6"pull-filter ignore "route-ipv6" You can workaround this problem by adding a comment marker at the end of each affected line, like: pull-filter ignore "ifconfig-ipv6" # pull-filter ignore "route-ipv6" #

@viragomann sorry how do I do that? How do I get to the configuration file? Basically, when doing a whatmyip, I want a WAN address of my VPN endpoint, not my actual IP address at home. Also, I would expect to see the VPN route reflected in a tracert if I'm not mistaken. Thanks

@viragomann Hi All port seems to be closed on pfSense, even they are not. I use and "port checker" (on internet) and it shows that ports are closed but they are not. I already disabled AV and Squid.

After reverting this changes https://redmine.pfsense.org/issues/12232 in file after update, active connections shows again in OpenVPN status.

@johnpoz Thanks

@bob-dig Thank you!

@dlogan No, this cannot be done in OpenVPN. I think, you could achieve this with two failover groups with inverted gateway priorities. But this requires two different OpenVPN servers on the main site.

If you want to fix this regression pls apply this patch 3ade222beb2cae2c0681ed69d4e5a0c82c6303f9

@jly2680 Same problem ? Then you should be able to find the answer here. Btw : you're late. 2.5.2 is past now, so is OpenVPN 2.5.2. It's pfSense 2.6.0 now, and OpenVPN 2.5.4. But, be happy, the issue stays the same. Depending your setup you use, some adjustments have to be made. As always, as everything, this needs the old way of finding solutions : look at the logs. Make the errors go away. Do what needs to be done.

@viragomann Thanks. Came here to report the final solution and I see you had answered with the same. The issue was that the default gateway was not responding to ICMP. Changing the monitoring IP to something else had immediately brought the Gateway up, and the routing now works as expected. This took way longer than it should :o

Hi, thank you all for your valuable input. I went with Cert+RADIUS to have extra layers of protection, like @TO2020 mentioned. This way I have a tad bit more security and a better integration into active directory where I manage all accounts.