Authentication OIDC Authentication VNS3 Licensing Access Management Clientpack Generation Installing HTTPS Firewall 2.0 Firewall AWS Specific features Firewall FWSets VNS3 Variables VNS3 Router IPsec Configuration IPsec Parameters VNS3 Peering Mesh Setting Topology Name VNS3 Overlay Network Snapshot Management VNS3 Event Alerting Network Address Translation Traffic inspection SNMP Support VNS3 BGP Configuration Guide Remote Support Resetting VNS3 Upgrading VNS3 Release Notes VNS3 EOL Policy and Milestones IPSec Connection Checklist VNS3 Known Issues VNS3 Specifications VNS3 VPN Client tools VNS3 Control Center VNS3 setup

AWS Specific features

Resetting Passwords via User Data

Occasionally the username/password to a VNS3 controller gets lost and users need a way to recover access to the controller.

The recommended/best practice way is:

1. Always have current VNS3 snapshot configuration files available. (This is not to be confused with what virtual machine snapshots). These are created via VNS3 Web UI or API.
2. Launch a new instance, change the username/password on the new instance to known items.
3. Now migrate from the instance which is unavailable to the new instance. See Migration Guide for more.

VNS3 now has an alternative, Amazon-only approach for customers without snapshot files, using Amazon instance “userdata”:

1. Stop the instance (this will create an outage!)
2. Modify the userdata by adding (as appropriate)

reset_api_password=mynewpassword
reset_ui_password=theapipassword

3. Restart the instance and login using the newly provided password.
4. An additional STOP / START of the instance will be required to remove the userdata, otherwise future password changes could be re-written by a future stop/start event.

Reseting Firewall via User Data

Occasionally access to the VNS3 Controller is lost due to an incorrect firewall entry blocking access. The recommended/best practice way is:

1. Always have current VNS3 snapshot configuration files available. (This is not to be confused with what virtual machine snapshots). These are created via VNS3 Web UI or API
2. Launch a new instance, change the username/password on the new instance to known items.
3. Now migrate from the instance which is unavailable to the new instance. See Migration Guide for more.

VNS3 now has an alternative, Amazon-only approach for customers without snapshot files, using Amazon instance “userdata”.

1. Stop the instance (this will create an outage!)
2. Modify the userdata by adding (as appropriate): reset_firewall=true. This will comment out all rules. They will not be deleted.
3. Restart the instance.
4. An additional STOP / START of the instance will be required to remove the userdata, otherwise future stop/start events could disable the firewall rules.