How to fix NET::ERR_CERT_AUTHORITY_INVALID with GoDaddy certificates
Newly issued certificates, like GoDaddy's R1, are not natively trusted by all systems yet. This triggers "NET::ERR_CERT_AUTHORITY_INVALID" or untrusted website warnings that block users from browsing the site or downloading clients. To fix the trust chain on picky servers like IIS, administrators must manually download specific intermediate or cross-root certificates directly from the GoDaddy repository.
Core Friction Pattern
Analysis of 3 peer accounts across online developer and community forums reveals that “How to fix NET::ERR_CERT_AUTHORITY_INVALID with GoDaddy certificates” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+4 alternative community-tested workarounds cataloged below.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
How to fix NET::ERR_CERT_AUTHORITY_INVALID with GoDaddy certificates
- 1Downloading and applying cross-signed certificate bundles or intermediate chains from the provider repository.Did this help you?
- 2Updating the trust chain in the trusted roots of the firewall or VPN host.Did this help you?
- 3Using external tools like ssllabs.com to verify the chain of trust.Did this help you?
- 4Installing cross-signed certificate bundles to ensure backwards compatibility with older client trust stores.Did this help you?
- 5Ensuring intermediate certificates are installed directly into the local machine's CA store rather than the user account.Did this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Some client reported "NET :: ERR\_CERT\_AUTHORITY\_INVALID" while browsing. Tested on Chrome on iPhone encountered same error but no problem on Edge of my desktop pc.”source ↗
“had a similar headache with godaddy certs and IIS a while back, the intermediate bindings in IIS can get weirdly picky even when the chain looks fine in mmc.”source ↗
“We have an R1 cert that is not natively trusted by all systems yet, so I have been having to download something from the GoDaddy repo (DV R1 With Cross to G2 includes Root) in order to fix the issue on other servers so that they will be trusted.”source ↗
“When users go to the website to download the VPN client the website is untrusted.”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
Why is it so hard to manage short-lived server certificates?
Short-lived SSL certificates force administrators to manually update keys across dozens of servers every few months. This overwhelming administrative overhead makes routine maintenance unsustainable and leaves systems at risk of frequent disruptions.
KB5124008 breaking domain trust?
Update KB5124008 breaks domain trust and causes connection status to flip unpredictably between true and false even after rebooting, repairing trust, and disabling machine identity isolation. Because remediation remains inconsistent, administrators cannot confirm whether the fix is actually working for end users to log in.
Why am I getting DMARC and SPF errors when emails deliver fine?
Third-party email marketing services often fail basic SPF checks within DMARC reports because their sending IPs are not included in your domain's DNS records, even though inbox providers still manage to deliver the messages. This discrepancy leaves administrators guessing about real deliverability health and creates confusing tool warnings that hinder proper configuration.
How do I install an SSL certificate on IIS?
Manually installing an SSL certificate and its intermediates on IIS often leads to errors where keys cannot be exported or requests cannot be completed correctly. This leaves site owners stuck with expired certificates when developers become unresponsive or guides fail, preventing them from securing their websites without direct hosting panel access.
Why are our Salesforce accounts getting blocked for high-risk proxies?
Legitimate network connections are being incorrectly flagged as high-risk anonymizing proxies like TOR or Mullvad, causing administrator accounts to be repeatedly blocked. This leaves organizations locked out of their accounts for months without a clear way to prevent the behavior.
Client sent me code to run locally is it malware?
Malicious actors on freelance platforms and LinkedIn trick developers into executing obfuscated code, repos, or installation scripts under the guise of project testing. This exposes local machines to compromise and prevents safe evaluation of client-provided repositories.