I had the same problem with this, and there wasn't much on the web to help
It turns out that the certificate that is generated during the install was created with the wrong date. i.e. the start date was 10-11 hours into the future of the install.
If I changed the clock (forward 1 day) on the vCenter server and workstation that I used to connect to the web client it would let me log in. I think it is a problem with time zones, something silly like win 2012 R2 applies the +10 hour offest (for Australia) and then VMware also added the +10 hours offest.
But this resolved it for me.