When in doubt...Reboot!
I think you run very little risk in rebooting your vCenter. Before you do it, try to ping your AD controllers by name to make sure DNS on vCenter is working properly. Also, if you're using AD via LDAPs, make sure the account configured in the vCenter Identity Source screen isn't locked out, disabled or has had its password changed. If you're using Integrated Windows Authentication, then now is a great time to switch to LDAPs as IWA is depreciated and no longer recommended.
Original Message:
Sent: Apr 03, 2025 02:44 PM
From: AlanRaczek1
Subject: sso logins fail on VCSA 7.0.x
Doing this from memory:
I cannot do a domain login with my VCENTER VCSA, administrator@vsphere.local works. I get a 401 error. I checked certificates and they all seem like they don't expire until 2030. This is an already running VCSA, so configuration is not the issue, this login (domain account) worked a couple days ago. Incidentally this same issue happened last week but mysteriously disappeared. A df on VCSA shows most partitions with plenty of room except /dev/mapper/archive_vg-archive which is at 95%. I am at a loss on where to look next. I will pick this back up tomorrow.
Can I SAFELY reboot this VCSA? There is no VSAN running, a pretty basic vCenter install with 3 ESXi's and a VCSA. But if a reboot is not a valid procedure at this point please tell me, Broadcoms articles don't do a lot of good.
...ar