How Can I troubleshoot my AWS VPN endpoint that stopped working?

0

We have a VPN set up and are using OpenVPN as the client to connect. This has worked with no issues until today. I don't see any outages that are relevant and the error message I'm getting is:

Lost connection to server : 1 times

Nothing has changed since I was able to connect that I know of and the VPC shows as available. What steps should I take next?

CJ
asked 6 months ago701 views
1 Answer
1

Troubleshooting a VPN endpoint in AWS that has stopped working can be approached systematically. Here are steps you can take to identify and resolve the issue:

  1. Check AWS Service Health Dashboard: Verify there are no reported issues on the AWS Service Health Dashboard that could be affecting the VPN service.

  2. Review VPN Logs: The first place to start is by checking the logs for your VPN connection. AWS VPN maintains logs that can be accessed through Amazon CloudWatch if they have been set up. Review these logs for any error messages or alerts.

  3. OpenVPN Logs: Check the logs for the OpenVPN client for any error messages that may indicate what the issue is.

  4. AWS Management Console: Log into the AWS Management Console and navigate to the VPC section. Check the VPN connections and ensure that the tunnel(s) are up and that there are no configuration changes.

  5. Network Connectivity: Ensure that your network connection is stable and that you can reach other internet resources. Sometimes the issue may not be on AWS’s end but with your local internet connection.

  6. Restart VPN Connection: Try restarting the VPN connection on your OpenVPN client. This can often resolve transient issues.

  7. Security Groups and NACLs: Check the security groups and network access control lists (NACLs) associated with your VPN and subnets to ensure that the necessary traffic is allowed.

  8. Update OpenVPN Client: Ensure that your OpenVPN client is up-to-date. Outdated clients may have issues connecting to the VPN server.

  9. Authentication: Verify that your authentication details have not changed. If you are using certificates, ensure they are still valid and have not expired.

  10. IP Address Changes: Check if the IP address of the VPN endpoint has changed. If you are connecting to an IP address directly, any changes might prevent you from establishing a connection.

  11. Restart VPN Endpoint: Consider restarting the VPN endpoint through the AWS console. A restart can clear up issues that are not apparent from logs or settings.

profile picture
ObiJan
answered 6 months ago
  • A lot of these points are for site to site VPNs. Not applicable for client VPN endpoints.

  • I appreciate this. I ended up just recreating the VPN client endpoint with the same info and the new one worked. Pretty disconcerting, but I really appreciate you taking the time to list out these steps.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions