VMware Cloud Community
jfvet
Enthusiast
Enthusiast
Jump to solution

Unable to log into vCenter 6.7 VMware Appliance Management page

vCenter 6.7 fresh vCenter Server Appliance install with an embedded Platform Services Controller on a 6.5 ESXi host.

Stage 1: Deploy appliance - Completed successfully

Stage 2: Configure appliance - Completed sucessfully

When I try to log in as root on the VMware Appliance Management web:5480 page using the IP address of the server, I receive the error. Unable to login, NOT the error Unable to authenticate user. I can successfully log in using the console with root credentials. Used a variety of browsers and validated security settings. Any ideas?

61 Replies
buggine
Contributor
Contributor
Jump to solution

Post 25 Works but the command is like this,

# service-control --start applmgmt 

don't use the .service,  he's just explaining its a service.

MarcoRamirez198
Contributor
Contributor
Jump to solution

Work for me, thanks.

Reply
0 Kudos
kingsxw
Contributor
Contributor
Jump to solution

Had same issue after  upgrade VCSA 6.7 U2 to U2b.

#service-control --start applmgmt

works but not a permanent solution, need to run again after reboot

This is my sultion:

#shell

into the shell

#systemctl list-unit-files

Found the applmgmt.service is in Masked status

#systemctl unmask applmgmt

unmask it

#systemctl list-unit-files

check it agin and should see applmgmt.service turned into Enabled status and should start correctly automatically after reboot.

dbutch1976
Hot Shot
Hot Shot
Jump to solution

Same problem, unable to authenticate.  This problem is utterly absurd.  Installing VMware-vCenter-Server-Appliance-6.7.0.31000-13643870_OVF10.ova on Workstation 14 Pro.

Reinstalled a dozen times, was initially trying to install a separate PSC, but after doing some reading decided to go Tiny vCenter with embedded PSC.  Same problem every time, I would set the password during the install however it would never accept it post install and I could not log in, simple message "unable to authenticate."

I did not specify either a SSO configuration password or a System Configuration password on my most recent attempt (just left them blank).  I was then able to log into the console using F2 and was prompted to set the password.  I set it to something simple, logged out, and logged back in.  That worked. I then changed the password a second time, logged out and logged back in, password working.  Only then was I able to log in via the web browser on 5480.  This issue and my resolution have me completely stumped, but I'm able to continue the setup at least.

I mean seriously....?

Reply
0 Kudos
RHari
Enthusiast
Enthusiast
Jump to solution

@Robert121281

I had exactly same issue

tail -f /opt/vmware/var/log/lighttpd/error.log

2019-09-16 23:51:46: (/build/mts/release/bora-11382773/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.523) no proxy-handler found for: /rest/appliance/system/version

2019-09-16 23:51:51: (/build/mts/release/bora-11382773/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1417) proxy - re-enabled: 127.0.0.1 8201

2019-09-16 23:51:54: (/build/mts/release/bora-11382773/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1041) establishing connection failed: Connection refused

2019-09-16 23:51:54: (/build/mts/release/bora-11382773/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1153) proxy-server disabled: 127.0.0.1 8201 8

When I looked at the services, found applmgmt and stopped vmware-statsmonitor

root@XXXXXX [ /var/log/vmware/applmgmt ]# service-control --status

Stopped:

applmgmt vmware-statsmonitor

Running:

lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-rhttpproxy vmware-sca vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon

I then followed https://kb.vmware.com/s/article/59476 to fix the issue.

If you find this answer helpful, please reward points by clicking "Correct Answer" or "Helpful Answer" Thanks, R.Hari
JeffNuhfer
Contributor
Contributor
Jump to solution

This fixed my service not starting.

Thanks kingsxw !!!

#service-control --start applmgmt

works but not a permanent solution, need to run again after reboot

This is my sultion:

#shell

into the shell

#systemctl list-unit-files

Found the applmgmt.service is in Masked status

#systemctl unmask applmgmt

unmask it

#systemctl list-unit-files

check it agin and should see applmgmt.service turned into Enabled status and should start correctly automatically after reboot.

shanet_69
Contributor
Contributor
Jump to solution

Hi

Try to login with Administrator@vsphere.local

Reply
0 Kudos
margitza
Contributor
Contributor
Jump to solution

This was exactly our problem after refresh the certificate of the VMCA!

After unmasking the service the service "Active: inactive (dead)". Restarting the service "systemctl restart applmgmt.service" the service is UP and RUNNING.

"systemctl status applmgmt.service" -> "Active: active (running)"

Retry login -> WORKS

Thanks

  Ralf

Reply
0 Kudos
realMasonman
Contributor
Contributor
Jump to solution

Had the same issue with message - Unable to Login.  Check that the service is running.  This worked for me:

Home > Administration > System Configuration > Services > Appliance Management Service  > Start or restart

If receiving message unable to authenticate user then try this page to reset your root password:

VMware Knowledge Base

Reply
0 Kudos
philma1
Contributor
Contributor
Jump to solution

Thanks, fixed my issue as well on many vCenter. It seems there is a bug with the updater lately.

Reply
0 Kudos
JuanAntonioVoui
Enthusiast
Enthusiast
Jump to solution

This work for me

Thanks

Reply
0 Kudos
Prabasi
Enthusiast
Enthusiast
Jump to solution

@kingsxw

You saved my day. Thank you.

Reply
0 Kudos
ntuckerbarbour
Contributor
Contributor
Jump to solution

Thanks! This solved my issue!

Reply
0 Kudos
swatpup102
Contributor
Contributor
Jump to solution

This should be the marked answer, worked for me right away.

Reply
0 Kudos
JuanAntonioVoui
Enthusiast
Enthusiast
Jump to solution

this work for me,

sometime later I've error again,

solved by migrate vCenter to another host,

surprise to me

Reply
0 Kudos
egiblockACO
Contributor
Contributor
Jump to solution

what worked for me:

SSH into the server.  check the status of the services:

[ ~ ]# service-control --status

Running:

lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-sca vmware-sps vmware-sts-idmd vmware-stsd vmware-topologysvc vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui

Stopped:

applmgmt vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-statsmonitor vmware-vcha vsan-dps

start the applmgmt service

[ ~ ]# service-control --start applmgmt

Operation not cancellable. Please wait for it to finish...

Performing start operation on service applmgmt...

Successfully started service applmgmt

all fixed.

NRay
Contributor
Contributor
Jump to solution

Reply
0 Kudos
AbdulBasitKhan
Contributor
Contributor
Jump to solution

Fixed the issue by checking the df -h and found that log disk was full, just increase the Hard Disk 5 and run a command to autogrow lvm of vcenter, and right after that issue fixed for me. the solution in this link worked for me.

https://www.bomzan.com/2021/10/12/vmware-vcenter-upgrade-error-no-space-left-on-device/

 

Thanks

Abdul Basit Khan

Stifflers
Contributor
Contributor
Jump to solution

It was really strange since we were quite sure the password for the root user was correct. File-based backup needed to be configured on the vCenter Server and as you know this configuration can be applied through the VAMI interface

Direct 2 HR

Reply
0 Kudos
Matthieu71634
Contributor
Contributor
Jump to solution

Hi,

I thank you for this one !

I deleted the file inside and restarted the service and it works !

Before that, I changed several times the root passwd, only the SSH connection was working.

Tags (1)
Reply
0 Kudos