vCenter Server Appliance 6.0 U1 - cannot access VAMI on port 5480

[bramclaeys]

Hi!

I successfully installed VMware ESXi 6.0 U1 Build 3073146 and then downloaded and deployed VMware vCenter Server Appliance 6.0.0 U1 Build 3018523.

The problem is that I cannot access the web interface on port 5480. IP address is pingable and the web client is working.

After reading some other topics I ran the command: netstat -plantu | grep 5480

Normal output would be (this is for a vCenter Appliance 5.5.0):

VCSA:~ # netstat -plantu | grep 5480

tcp        0      0 :::5480                 :::*                    LISTEN      2486/vami-lighttpd

Output on my system:

VCSA:~ # netstat -plantu | grep 5480

Could anyone help me to solve this issue?

[VMpalavsachin27]

The vcenter 6 does not have 5480 port for management, instead it has Web UI or Appliance Shell or DCUI which looks much like ESXi DCUI.

Thanks

Sachin P

[bramclaeys]

It does has a web interface on port 5480,

I am revering to this:

"Appliance Management User Interface: An all new HTML5-based management interface for the appliance at https://<FQDN-or-IP>:5480."

Source: Updating vCenter Server Appliance 6.0 to Update 1 - VMware vSphere Blog - VMware Blogs

The problem is, I cannot connect to this website. I get the error: "This page can't be displayed".

[bramclaeys]

I redployed the vCenter Appliance 6.0 U1 and now everything is working!

I can now go to the website https://<FQDN-or-IP>:5480.

[garclayton]

We are having this same issue after the upgrade to U1. I wish it didn't come down to redeploying our vCenter appliance. bramclaeys, did you have any other information from when you experienced this issue?

[garclayton]

Poking around the internet I found this...

VMware Virtual Appliance Management Interface (VAMI) and URL-based patching - Returned back in VCSA ...

Basically you need to edit the config file for lighttpd and set IPv6 to disabled if you have done so on your vcenter console after the upgrade. Otherwise you cannot access VAMI after the upgrade

[bramclaeys]

I never did an upgrade. I immediately deployed the version 6.0 U1.

I removed my previous deployed vCenter and also cannot replicate the problem, so I cannot test your solution. But for me it looks like he had the exact same problem, so the link can be helpful for other people.

Thanks anyway for the reply!