Virtual thoughts – Random comments on the IT industry: vCloud Director 9.1 for Service Providers Installation and Firewall Issues
As I recently installed vCloud Director 9.1 for Service Providers, I encountered a “by design” issue that may cause some headaches for new users. In this blog post, I’ll share my experience and the solution to the problem I faced during installation.
vCloud Director Installation and Empty Webpage
During the installation of vCloud Director on a CentOS 7 VM, everything went smoothly until I tried to access the web page after completion. Instead of seeing the vCloud Director login page, I was greeted with an empty webpage. This issue is not uncommon, and it’s due to a firewall configuration that needs to be adjusted.
Required Linux Packages
Before installing vCloud Director, make sure you have all the required Linux packages installed on the VM. In my demo/test environment, I’m using self-signed certificates, but in a production environment, you should use real signed certificates.
Database Connection and Firewall Issues
I had no problem connecting to the database server (again, since my environment is for demo, I’m using Microsoft SQL Server Express 2016 – not supported in a production environment) or the vCD server (to both HTTP and console interfaces) using either IP address or FQDN. However, I encountered issues with connecting to the webpage. It smells a bit like a firewall issue?
Logging and Debugging
To troubleshoot the issue, I started by looking into the logs using the command `tail -f /opt/vmware/vcloud-director/logs/vmware-vcd-watchdog.log`. The log output showed a warning “Server status returned HTTP/1.1 503”. This indicated that there might be an issue with the firewall configuration.
Firewall Configuration
To verify the active firewall rules, I used the command `sudo firewall-cmd –zone=public –list-services`. Only the ssh and dhcpv6-client services were enabled. It seems we’re missing a few services, so I enabled them using:
`sudo firewall-cmd –zone=public –add-service=http`
`sudo firewall-cmd –zone=public –add-service=https`
Verifying the new firewall rules using `sudo firewall-cmd –zone=public –list-services` showed that the services were now enabled and allowed.
Restarting Services
It’s a good practice to restart the services after making changes to the firewall configuration. I stopped the vCloud Director service using `service vmware-vcd stop` and then started it again using `service vmware-vcd start`.
After a successful restart, reopening the browser brought me back to the vCloud Director login page, and I was able to continue configuring the platform.
Conclusion
In conclusion, when installing vCloud Director 9.1 for Service Providers, it’s essential to ensure that all required Linux packages are installed and that the firewall configuration is correct. This issue may cause some frustration, but with the right troubleshooting steps, you can resolve it quickly. Remember to restart the services after making changes to the firewall configuration.
I hope this blog post helps you avoid any potential issues during your vCloud Director installation. If you have any further questions or comments, please feel free to leave them below.