Experiencing an issue with you Vault/Consul/Nomad not responding? Here are some tips on how to resolve this issue.
If you returned to your session and the machine running the bastion was in sleep mode, the jobs may need assistance with restarting.
- Run the command
genvid-bastion restartto force restart the jobs.
If the problem persists, verify if there your Firewall or Windows Defender is blocking it.
- Windows should normally address this by triggering a popup message when you run
genvid-bastion install. Separate popups should appear to give permissions (or deny them) for each Consul and Nomad.
- You can also temporarily disable the firewall.
If the popups don’t appear on their own, you may need to add an Inbound Rule manually in the Windows Defender Firewall settings.
- Open Windows Defender Firewall with Advanced Security.
- Click Inbound Rules in the left menu bar.
- Click on New Rule… in the right menu bar.
- Select Program, then click Next.
- Paste the path to each of the jobs which are found in the /bin folder inside the Genvid installation folder, then click Next.
- Example: C:\Genvid\Genvid Technologies SDK 184.108.40.206\bin\consul.exe
- Select Allow the connection, then click Next.
- You may select any of the checkboxes depending on your security restrictions, then click Next.
- Name the rule based on the job you’ve selected at step #5, then click Finish.
You can repeat these steps for all other jobs/processes you wish to allow.