LSDOCTOR ERROR _getSslCert: Got connection refused when getting cert on 443! Is rhttpproxy running?

[serginegre]

Hello everyone,

 

I'm migrating my old vCenter 6.7 to v8. I'm having certificate errors that I can resolve with lsdoctor (old vCenter 5.5 certificates and the STS machine san missing). However, when I run lsdoctor, I get the error: ERROR _getSslCert: Got connection refused when getting cert on 443! Is rhttpproxy running?

 

rhttpproxy is running correctly. I think my problem is because my vCenter's SSL port is 444 (not 443). Does anyone know of a solution?

 

Thanks everyone

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

[ldclancy2]

Certs are not my strength, but there is a newer cert tool...

vCert - Scripted vCenter expired certificate replacement

Looks like it is only for vCenter 7+, so maybe you have to get to version 7 first... and then onto version 8?

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

[serginegre]

Thanks for your reply.

 

I tried migrating vCenter to version 7 and I'm getting the same error.

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

[Dawid Dudek]

Did you confirm that rhttpproxy service is up and run on default port (because LSDoctor use it).
You can check it via ssh on vCenter:
service-control --status rhttpproxy
if not running you can try start it:
service-control --start rhttpproxy

If it not starting check certificates (if they are valid):
for store in $(/usr/lib/vmware-vmafd/bin/vecs-cli store list); do echo "Store: $store"; /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store $store --text | grep -ie "Not After"; done
or download and use "check-sts.py" from kb.

Maybe there is a problem with LSDoctor version to old / new for your vCenter version.

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

[stranger267]

We had similar issue, if system had very old time configured. So, if system refuse to connect, then make sure that system have correct time, before all other tests.

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

[serginegre]

Hi stranger267,

Thanks for your reply, I've checked the time and it's correct, connected via NTP

Regards

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

[serginegre]

Hi Dawid,

 

Thanks for your reply. I've verified that rhttpproxy is running, restarted it, and the problem persists.

 

I've checked the certificates, and they're all valid except for one that's expired. It's an outdated certificate from vCenter 5.0 and is for VMware vSphere Profile-Driven Storage Service.

Regards

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