OpenVPN AS not responsive on public ip address

[jimstowe]

At least 50% of the time my installation of OpenVPN AS 1.8.3 becomes unresponsive on the public ip address. I'm running it on a fully patched CentOS 5.7 and I've completely disabled the firewall in order to eliminate that as a possible culprit. The private NIC remains responsive. However, when I attempt to use a web browser or the OpenVPN client to connect to the public address it fails. This is very frustrating and I can't deploy a solution unless it is up consistently. I've opened a ticket with support, but haven't had any response in 48 hours.

The error message the client gives is: "Unable to obtain Session ID from vpn.m*****.com, port(s)=443: XML-RPC: TimeoutError.

I tried it multiple times yesterday and it worked each time. Today, it has failed each time I've tried to connect. Any help would be greatly appreciated.

[vmachine]

are you using carp failover on the public IP? Is the openvpnas service still running when you get that error? have you check the vpnserver logs /var/logs for other errors? I'm about to deploy 4 OpenvpnAS servers and im having some annoying issues as you have seen my posts. mainly not being able to restrict users when using LDAP. so anyway answer the questions above and i will see if i can be of any assistance.

[jimstowe]

I'm not using carp failover (I didn't know what it was until you mentioned it and I did some research). I've looked at the openvpnas.log file and there are no errors. I just tried to connect, got the same timeout error, and double-checked the log - no error.

I'm not sure what is more frustrating; the lack of reliability or the lack of response from the company. Still no response to my "official" support ticket and I'm using the paid version of the product.

[vmachine]

Not sure what's happen there...you can try revoking the client certificate and get a new one.. it seems as if the cert is currupted.