Working on upgrading our vCloud Air TMM lab today, I came across an interesting error that had me baffled for quite some time.
I was upgrading the vSphere Replication Appliance from version 5.8 to version 6.0 and everything went smoothly. After logging out and clearing the cache for the web browser (as documented here), I came across a new field that needs to be configured for the vSphere Replication Appliance to work. Its the LookupService Address. This didn’t exist in the previous version, but easy I thought. Lets enter the vCenter server FQDN and away we go.
vSphere Replication Unable to obtain SSL certificate
Then I received the error:
Unable to obtain SSL certificate: Bad server response; is a LookupService listening on the given address?
If you perform a quick google, you are reffered to this KB article, but DNS wasn’t the problem, I could ping both the long FQDN and also the short name. So I knew it wasn’t that.
Then the vCenter Runtime settings were mentioned, so I checked this, and yes these were incorrect. I updated the vCenter Runtime settings, but still the error persisted! What am I doing wrong I thought? This should work easily.
After thinking about this for a moment, I realised my own ridiculous error. I was not entering the full lookupservice address for the vCenter server.
The full Lookupservice address is: https://[FQDN_vCenter_Server]:7444/lookupservice/sdk
After changing the vCenter Server lookup address to the correct one, everything worked perfectly, and I received the Sucessfully saved the configuration message! Phew!!
Thats it. Once configured you can go and start configuring Virtual Machine replication.