Had an issue with the SSL certificate just locally as well @inthedeepend . So got a
Your connection is not private
Attackers might be trying to steal your information from domain.dev (for example, passwords, messages, or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID
I also saw in the inspector the following on the certificate:
Subject Alternative Name Missing
The certificate for this site does not contain a Subject Alternative Name extension containing a domain name or IP address.
as well as :
There are issues with the site's certificate chain (net::ERR_CERT_COMMON_NAME_INVALID).
and provision once more.
So checked the certificate in the keychain and that still seemed to be OK and accepted. Did not see any error in the logs that could help. Internet is up and running. Looking into a manual way to get a new certificate now. Provisioning again does not seem to help.
I needed to remove:
as I did not set up www. Re-added this after a Trellis upgrade and had removed it for production already. Just not for development. After I changed this and provisioned once more all was not well though and, well, I had a new error:
This server could not prove that it is domain.dev; its security certificate is from [missing_subjectAltName]. This may be caused by a misconfiguration or an attacker intercepting your connection. Learn more.
Reading about this new error at https://superuser.com/questions/1202498/create-self-signed-certificate-with-subjectaltname-to-fix-missing-subjectaltnam atm..
I can however choose now to continue to site at least..
Hmm @fullyint mentioned at https://discourse.roots.io/t/letsencrypt-error-on-fresh-install/8438/2 that I should use self signed or nothing on Vagrant VM's as verification cannot be made. And that using none is better. Did work before though. Will provision without now..