Hi,
Sorry, what is your guest OS and what is your host OS?
Do you mean you can't connect to ANY https website in chrome, or is it specific for some appliances that you run?
Not sure what the openssl output is supposed to say? Are you getting this from a normal cert like google dot com and it comes back as a self signed cert or is it showing that "it works with openssl, but not with chrome?"
FWIW, no this is not something that has been reported by others.
--
Wil
John,
So in recap, you're using the browsers at your host OS to connect to VMs on your VMware Fusion?
I was confused as initially I read it as that you were having issues using a browser from within one of your VMs..
The error CERT_COMMON_NAME_INVALID means that you are not connecting to the hostname for which the VM has a certificate.
eg. If you create a certificate for example.com, but you then connect to it via httpx://10.10.10.1 instead of httpx://example.com that you will see the above error. The name has to match the certificate for which it was created. If you created a cert for an IP address then that IP address cannot change. You will have to generate a new certificate.
Please note that I write httpx instead of https to not trigger the antispam filters on this forum.
You might be well aware about the above, but that's basically what the error is about.
With openSSL you can test for the common name like this:
openssl s_client -showcerts -servername example.com -connect example.com:443
Another way to test the certificate is using curl:
curl -L -v -s https://www.example.com 1>/dev/null
SSH normally throws an error about that the IP has changed and not just "disconnect", but that depends on the configuration and IIRC it normally only asks once with a Yes/No question.
--
Wil
John,
Gotcha, the connection reset is peculiar.
A few more questions.
Are you running a host based firewall on your mac?
Like Little Snitch, or Lulu or something else?
Just wondering if there's a possibility of something else that can influence the connection.
Another detail that I'm missing is if your VM's are using a bridged, NAT or host typed network configuration.
Seeing a vmware.log file from one of those VM's might also help as it helps answering more questions.
--
Wil
Hi,
A few remarks.
The virtual hardware of the VM is version 10, which is very very old, I would suggest to switch it to a more recent version.
I also note that the VM has 4 vCPU's on a host which has only 4 physical cores (threads don't count). This means that it is likely that the host runs out of resources and as such your network resources might not be sufficient. The virtual network adapter uses CPU in order to route packets. So I suggest to drop the VM to use 2 vCPUs and see if that helps, if only for isolating the lack of available resources as a potential issue.
I also see that the guest OS is set as "Other-64" which is an odd choice and strongly recommend to have the guest OS type match the actual guest OS more closely. You never answered my question on what guest OS is running so I cannot make recommendations on that.
The network card is set to vmxnet3. That normally is the best choice, but it depends entirely on the guest OS used... you could try to change it to an e1000e type NIC and see if that helps.
--
Wil