This Walk through goes over how to use an NGINX reverse proxy to simplify access to a VMware Holodeck environment by bypassing WebTop and providing direct access to VM consoles, VCF services, and ESXi hosts.
The attched script automates NGINX reverse proxy configuration on the HoloRouter for a Holodeck VCF lab. It generates SSL certificates, rebuilds NGINX configurations, enables SSH forwarding, and publishes internal VCF components through a single external IP address, making lab access significantly easier for engineers and administrators.
Prerequisites
SSH to the HoloRouter and ensure the following files are located in the same directory:
holodeck-vars.conf
setup-holorouter-proxy.sh
Note: Rename the variables file to holodeck-vars.conf
Configuration
Edit the environment variables as required:
- Open holodeck-vars.conf
- Update hostnames, domain names, or IP addresses if your environment differs from the default Holodeck deployment
Installation
Run the script as root:
chmod +x setup-holorouter-proxy.sh
sudo ./setup-holorouter-proxy.sh
Post-Installation
After the script completes:
-
- Copy the hosts file entries displayed in the output.
- Add them to your local hosts file:
C:\Windows\System32\drivers\etc\hosts
-
- Flush the Windows DNS cache:
ipconfig /flushdns
Validation
Verify access to your VCF components through the reverse proxy:
- vCenter: https://vc-mgmt-a.site-a.vcf.lab
- ESXi Host: https://esx-01a.site-a.vcf.lab
If configured successfully, you should be able to access vCenter, ESXi hosts, NSX, SDDC Manager, and other VCF services directly through the proxy without using WebTop.