VMware Cloud Community
mafnan1
Contributor
Contributor

Vcenter is not accessible

Dear Support

 

My Vcenter is not accessible and it is showing this error . I tried all methods including restarting services but failed. Its a productions server ESXI 7.0 . Please provide me support

 

Thanks 

Reply
0 Kudos
7 Replies
a_p_
Leadership
Leadership

Without knowing at least some details it's not easy to advice.

Anyway, please see whether the information in https://kb.vmware.com/s/article/83161 may help.

André

PS: Please note that this is a user community, not the official VMware support.

Reply
0 Kudos
mafnan1
Contributor
Contributor

I need customer support to figure out the reason. I am using paid solution of vmware 

 

 

Thanks 

Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee

Support: https://www.vmware.com/support/contacts.html

 


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos
basteku73
Enthusiast
Enthusiast

check if dns is working :winking_face: 

regards, 
Sebastian

Reply
0 Kudos
RajeevVCP4
Expert
Expert

External PSC or Embedded ,

Which version

If external PSC follow these step

Shutdown vcenter server

Shutdown PSC

Power on PSC and check all service must be running then

Power on VC and wait 10-15 minutes then check services status

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
Reply
0 Kudos
Alex_Romeo
Leadership
Leadership

Hi,

To check if the STS certificate is expired, follow the kb: https://kb.vmware.com/s/article/79248

If the STS certificate has expired, please follow this kb: https://kb.vmware.com/s/article/76719

 

regards,

 

Alex_Romeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
nordhuus
Contributor
Contributor

Spoiler
I have had the same issue and this is how we solved it:

https://kb.vmware.com/s/article/83161


Reply
0 Kudos