Added certificate and hostname - now clients can't connect

nmcwilli

Hi guys,

I've added a certificate via the web server configuration page, and then changed my IP address to a domain on the Server Network Settings ... now my VPN clients can no longer connect.

I'm just getting timeouts now. Looks like its authenticating, and then just eventually timing out.

Seems like if I switch things back to the IP Address my clients can connect fine. Is there a step I'm missing? I'd like them to use the hostname and certificate preferably.

access server version 2.1.9

The Johan

When you download and install the connect client, it gets instructions on where to connect to then and there. It doesn't update afterwards by itself. So in theory changing the field 'host name or IP address' on the server has absolutely no effect on an already installed client.

In any case, check this page;
https://docs.openvpn.net/troubleshooting/troubleshooting-client-vpn-tunnel-connectivity/

nmcwilli

yeah i saw the notice on the admin page that i'll need to download and install the connect client again. i tried that and when i install the new connect client, it does show that it points to the domain ... but still times out.

I'm on mac osx sierra ... is it possible that some sort of incorrect config is hanging around from the last install?

Neil

The Johan

See the client side log file.

nmcwilli

hey guys, don't bother to post my last post. figured it out.

long story short, but i made things much more complicated for myself by created an amazon elastic load balancer and having all traffic route through that which caused conflicts with my certificate issued in my openvpn server. so yeah, lesson learned. don't use an ssl certificate w/ amazon load balancers with your openvpn instance.

The Johan

Aha. Okay. So using the host name made it go through the load balancer and encounter problems, while using IP made it bypass the load balancer and work normally. That makes sense. Thanks for sharing.