I recently moved my virtualization lab from a hosting company to an Intel NUC cluster here at home.
While I was experimenting around with my naming convention and my internal DNS, I had to rename one of my ESXi hosts. At that point, I did not have set up a vCenter Server Appliance, so I decided to rename the host as it was described in KB 1010821. I then re-generated new self-signed certificates and rebooted the host.
After that everything seemed to work fine. Everything but the web console. I tried to to use the Remote Console with VMware Fusion and got the following error message:
At first I thought that the SSL certificate was cached, or that somewhere in the system the old certificate was not replaced. But the error shows, that the server name was still the old one, the cert was new and matched with the new hostname. Then I realised that the username in the top right corner was using the old hostname as well.
Second thought was some kind of caching error. So I cleared my cache and cookies and tried two other browsers, to no avail. After I spent some time one the console, I was not able to find a database or a configuration file that would contain the old value. I was ready to give up, ready for a reinstall.
As a last attempt I went to the web site of the Host Client Fling and looked for a new version. Maybe a bug? I removed the old version 1.23 and installed 1.28, but the error was still the same. I began reading the comments and the bug section, and after a while I eventually found this bug description that matched with what I experienced.
I checked my 1Password entry and finally found the culprit. 1Password did the same LastPass did for the bug reporter. It saved the FQDN which was within a hidden field on the login page. And every time I logged in, it would fill out the hidden form with the old FQDN and mess up the ESXi Host Client. Problem solved. Now I can continue installing and configuring the new lab environment!