pfSense

hi Chris, i am using the latest version. another way is update the "local ip address" in /var/etc/openvpn/server1.conf file manually through shell.
I am not sure whether if the IP address of the "local" variable should auto updated according to the interface change as there is no option for user to change the "local" variable through the web interface.

what type of WAN?

Any type

I know that's not true, lots of dynamic WANs out there running OpenVPN that update correctly. What exactly are you doing to replicate?

Below is the steps to replicate the issue:
1) Assign an IP address to a WAN interface.
2) Create a OpenVPN server and select the WAN interface as its interface.
3) Assign an new IP address to the WAN interface.
4) Stop and Start the OpenVPN service through web page.
5) System log will show the error i mentioned earlier. The "local" variable in server1.conf still keeping the previous IP address.

In addition to this, it seems that the interface selection does not work with virtual IPs at the moment (it still assigns the default interface IP and not the virtual IP). This did work in 2.0.1 and in earlier 2.1 snapshots.

I also had this same issue, although I'm using 2.0.1 AMD64 release on a virtual machine under VMWare ESXi 5.0.0. We recently changed static blocks and had to reassign interfaces. Our peer-to-peer OpenVPN server services updated fine after a reboot but I had to manually change the server .conf file for our remote access OpenVPN server service. This was not on the primary WAN interface, we use a secondary for remote access. We have 4 total, with the remote access server being the only one that had issues.

I should clarify. We have 4 OpenVPN server instances total on this particular pfSense box, with the remote access server service being the only one that did not update it's local IP.

I just changed my WAN on a test system from DHCP (which had 192.168.9.101 at the time) to a static IP (192.168.9.99) and added the gateway (192.168.9.1) (this test system is hanging off my home router, whose LAN is 192.168.9.0/24). An OpenVPN client that was up, went down. /var/etc/openvpn/client1.conf still had the line:

local 192.168.9.101

local 192.168.9.99

Oct 5 18:39:20     openvpn[60557]: Inactivity timeout (--ping-restart), restarting
Oct 5 18:39:20     openvpn[60557]: SIGUSR1[soft,ping-restart] received, process restarting
Oct 5 18:39:22     openvpn[60557]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Oct 5 18:39:22     openvpn[60557]: Re-using pre-shared static key
Oct 5 18:39:22     openvpn[60557]: TCP/UDP: Socket bind failed on local address [AF_INET]192.168.9.99: Can't assign requested address
Oct 5 18:39:22     openvpn[60557]: Exiting
Oct 5 18:39:22     openvpn[60557]: /usr/local/sbin/ovpn-linkdown ovpnc1 1500 1560 10.9.1.2 10.9.1.1 init

Update to my original issue. After editing the /var/etc/openvpn/server1.conf file with a the new IP everything worked until... a reboot. I now have two "local" entries. One with the new IP and one with the original IP. Of course the service fails with both of these entries in there. Where else are these static IPs saved?

I was running into this when selecting a Failover Gateway Group as the outbound device for the OpenVPN connection, running on latest 2.2.2.

Happy to perform any steps/checks to help you guys reproduce...