With some great help from @redblue, we’ve possibly made a bit of a breakthrough on this one. The vast majority of Local users, even those using Mac OS Catalina, haven’t been running into the certificate revocation issue in the latest versions of Local but a few still are and we want to try to make some headway for those folks that have been running into this.
@redblue was able to send us over the .cer file that was being revoked in Chrome. From there we were able to spot that Avast was being injected into the Certificate’s Common Name and Organization fields for the Issuer. This was breaking the certificate from the point it was even issued and no amount of overriding it through Keychain exceptions made any difference.
When we identified this, he noted that Avast has been installed on his computer for quite some time but only recently did this problem arise. We had created a certificate that did not have this information, which didn’t work out of the gate but @redblue responded with this:
In the meantime, I went ahead and replaced the linewise.local cert with the one attached. Unfortunately, that doesn’t seem to have had any effect. But THEN, I deleted that cert and regenerated one through Local, which did actually work – first time in about a month that a cert for a local site has been valid. I realize this probably raises more questions than answers, but this is something I’ve tried before as well.
We don’t have a complete solution yet but we would like to try to explore this particular avenue with other folks that are still being affected with the certificate issues in Local (after installing the latest version).
If you are still experiencing this issue, please check to see if you have any Antivirus/Firewall software running, temporarily close/disable them and try to remove/re-issue a certificate within Local. If you still have problems, would you be able to manually inspect your certificates or upload it?