A VPN portal on an ASA started showing Not secure in Chrome. The certificate looked fine: a GoDaddy wildcard, valid dates, correct name.
Table of contents
What was going on
In 2026 GoDaddy moved DV certificates to a new hierarchy. New certificates are issued by GoDaddy TLS Intermediate CA DV - R1v1, which chains up to GoDaddy TLS Root CA - R1. That root is new and isn’t in every browser and OS trust store yet.
To cover the gap, GoDaddy publishes a cross-certificate that links R1 back to its older, widely trusted G2 root. Browsers can build a trusted chain only if the server sends that cross-certificate.
The ASA was sending just two certificates, the leaf and the R1v1 intermediate, so Chrome had no path to a root it trusted and showed NET::ERR_CERT_AUTHORITY_INVALID. Edge on Windows worked, because Windows already trusted R1.
How to confirm it
openssl s_client -connect vpn.example.com:443 -servername vpn.example.com -showcerts
If the chain ends at GoDaddy TLS Intermediate CA DV - R1v1 and the last issuer is GoDaddy TLS Root CA - R1, the cross-certificate is missing.
The fix
- Download the R1-to-G2 cross certificate (
gd_tls_root-r1-cross-g2) from GoDaddy’s repository at certs.godaddy.com, in PEM format. - Add it to the ASA as a CA certificate so it’s available to complete the chain:
conf t
crypto ca trustpoint GD_R1_CROSS_G2
enrollment terminal
no ca-check
crypto ca authenticate GD_R1_CROSS_G2
<paste PEM cross certificate>
quit
write memory
- Run the
openssl s_clienttest again. You want three certificates: the leaf, R1v1, andGoDaddy TLS Root CA - R1issued by the G2 root.
If the ASA still sends only two, export the identity trustpoint as PKCS12, rebuild it with OpenSSL so the file includes the cross certificate, and import it again.
Takeaway
Any device that received a GoDaddy DV certificate after mid-2026 may have the same problem, even if nobody has complained yet. Check each one with openssl s_client. Or skip this class of problem by moving to a CA whose root has been trusted for years, such as Let’s Encrypt.