kavise
Hello,
Is it possible to configure an instance launched with the OpenVPN community ami so that when the instance is shut down and restarted (with a new IP), OpenVPN can still work?
To save cost I don’t use Elastic IP, rather I just use the default public IP which changes when you restart the instance.
If the instance could be made to automatically read its public IP on startup and apply it, that would be best - However even if I had to manually log in and edit a config file with the new IP, that would be fine. As it is now once I stop the instance and restart it, I can’t log into it any more using Putty from Windows and the new public IP.
Thanks much for any help
OpenVPN Access Server 2.6.1 - ami-03cbd6eb900df8dff
This is resolved - I was able to change the IP from the Admin Portal - I discovered that I lost a subnet route table association which is why I could not connect, once I was able to connect it was quick to resolve
