FalseTB
I'm sure this is a tired topic - the search results show a ton of posts, none of them fit this situation that I could see however.
I HAD it working. All I did was disable the link to determine if one of the connections was having a problem (it is) and now it won't come back up again. It's been 45+ minutes since I enabled both sides of the pfsense openVPN, and *nothing*. There's no link up, and the control panel keeps saying "No OpenVPN instance defined" (and pings to either network from either side don't work)
pfSense's implementation of OpenVPN seems to be really poor. If I could afford half the modules in Untangle that pfsense lets me have to free, I would have switched ages ago.
Anyone? I'm so tired of fighting this tonight.
Superman859
I'm working on getting it running under pfSense and am not having your issue (although still having an issue.) I can connect to the VPN from local network but not external. Either way, I don't have any issues starting openvpn.
The main thing I've found useful so far in debugging the openvpn issues is to ssh to your pfsense box and work with openvpn manually in the meantime.
To kill running instance:
kill `pgrep openvpn`
To start again:
/usr/local/sbin/openvpn --config /var/etc/openvpn/server1.conf
This is where everything is for me anyways and I just set it up through pfsense GUI. Editing server1.conf to remove it from daemon mode can help speed things up, as well as change verbosity. Sounds like for some reason process may not be starting, and working through terminal typically reveals those issues better than the pfsense GUI.
