Troubleshooting VPN Connection Timeouts

If you experience VPN connection timeouts or see errors indicating that "the connected party did not properly respond after a period of time," this may be due to an AWS status check failure requiring a system reboot. Following fault is seen on duplocloud portal: VpnAuthWorker Main function of the worker threw an exception: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond Common Symptoms VPN connection loads but then times out Unable to access admin portal Connection failure messages in VPN logs Resolution If you encounter these issues: First, verify that you can access your admin portal (typically accessed via your designated admin URL) If access issues persist, contact support to check for AWS status check failures A system reboot may be required to resolve the connection issues Note: After the system reboot, allow a few minutes for all services to restart before attempting to reconnect to the VPN. Prevention To proactively monitor for these issues, ensure you have proper monitoring set up for: AWS Status Check alerts VPN connection status System connectivity checks