Allow no hostname to be specified

virtualjj / automated-openvpnas

AWS CloudFormation template to automate a more secure deployment of the OpenVPN Access Server Community Edition.

MIT License

21 stars 17 forks source link

Allow no hostname to be specified #10

Closed jpike88 closed 6 years ago

jpike88 commented 6 years ago

Sometimes, we use IP addresses for the VPNs and don't bother with hostnames.

With a hostname specified, it should default to the static IP that was assigned at the time of instance creation.

Otherwise this error fires when attempting to connect on the portal:

API Error: exceptions.IOError: ProfileReader: error obtaining profile_id '13_115_78_249_u1109': [Errno 2] No such file or directory: u'/Library/Application Support/OpenVPN/profile/13_115_78_249_u1109.ovpn'

virtualjj commented 6 years ago

Noted - thank you for the input. I will update the documentation so that the user can make the choice as some users will probably add a TLS cert which requires a hostname.

virtualjj commented 6 years ago

I could duplicate this issue. This appears to be related to post configuration which is out of scope of this template per the Caveats section of the README.md:

Also, I haven't included any examples of how to connect to the OpenVPN AS instance after it is deployed so the assumption is that if you are deploying an OpenVPN AS instance you know how to configure and connect the VPN client.

Entered an IP Address:

Stack launched successfully. Grabbed the admin portal connection URL:

Successfully connected, clicked OK:

Admin console launched without issue: