msk05
Enthusiast
Enthusiast

vCDA is not accessible through vCloud diector admin portal

Jump to solution

vCD - 10.1.2

vCenter - 6.5 U3

VMware cloud Director Availability - 4.0.1

vCDA is deployed as a combined appliance. As you can see below the available vCDA plugin in vCD

pastedImage_0.png

When we click on vCDA plugin getting below error

pastedImage_1.png

I see below error in /opt/vmware/h4/cloud/log/cloud.log

2020-10-01 06:17:17.816 ERROR - [UI-f1c69f06-2dbd-4c72-b175-e450fdf2ff48-7N] [https-jsse-nio-8443-exec-8] c.v.h.c.d.BaseDiagnosticsService         : Idle.

Attached the log bundle. Please guide me what I am missing here

0 Kudos
1 Solution

Accepted Solutions
msk05
Enthusiast
Enthusiast

I followed the checklist to configure vCAD when I had the issue. I redeployed it following the VMware documentation Configuring the Cloud Appliances  and I was able to access the plugin via vCD now

Here I noticed two things during the redeployment however I am not sure what caused the issue.

1) In new deployment while configuring cloud service I used IP address and port 443 as per the documentation "Enter the VMware Cloud Director URL as https://VMware-Cloud-Director-IP-Address:443/api"

2) In old deployment I believe I missed the tunnel configuration in https://Appliance-IP-Address:8442/ui/admin as it was not part of initial checklist however the system monitoring showed all green.

View solution in original post

0 Kudos
3 Replies
paluszekd
VMware Employee
VMware Employee

I presume you are using a self-signed cert, correct? Click on that link (that is your URL endpoint or tunnel endpoint) and accept the cert. From there, the plugin will populate. This is expected behavior when using self-signed certs.

0 Kudos
msk05
Enthusiast
Enthusiast

Yes, its self signed certificate. I tried this in multiple browser and when I click on tunnel endpoint URL I am able to access it without any warnings still I get the same error.

0 Kudos
msk05
Enthusiast
Enthusiast

I followed the checklist to configure vCAD when I had the issue. I redeployed it following the VMware documentation Configuring the Cloud Appliances  and I was able to access the plugin via vCD now

Here I noticed two things during the redeployment however I am not sure what caused the issue.

1) In new deployment while configuring cloud service I used IP address and port 443 as per the documentation "Enter the VMware Cloud Director URL as https://VMware-Cloud-Director-IP-Address:443/api"

2) In old deployment I believe I missed the tunnel configuration in https://Appliance-IP-Address:8442/ui/admin as it was not part of initial checklist however the system monitoring showed all green.

View solution in original post

0 Kudos