Go Daddy SSL For Zyxel Flex 100 Question

Options
JCE
JCE Posts: 21
First Comment Friend Collector Sixth Anniversary
image  Freshman Member

Hi We have used Go Daddy SSL certificates for the last 3 years for our Flex 100.

When we came to rekey our certificate today it only seems to allow ServerAuth and no longer supports ClientAuth

And instead of saving the issuer as Go Daddy Secure Certificate Authority G2 it now says GoDaddy TLS Intermediate CA DV R1v1

This then causes the SSL to be untrusted when logging in to the zyxel

Is there a solution or do we have to ditch using GoDaddy

Many thanks for any guidance.

All Replies

  • Zyxel_Judy
    Zyxel_Judy Posts: 2,851
    Zyxel Certified Network Engineer Level 2 - Nebula Zyxel Certified Network Engineer Level 2 - Switch Zyxel Certified Network Engineer Level 2 - Security Zyxel Certified Network Engineer Level 1 - Nebula
    image  Zyxel Employee
    Options

    Hi @JCE ,

    You don’t need to ditch GoDaddy — this is a CA chain transition issue, not a certificate problem. Your WebGUI login only needs “Server Authentication.” ClientAuth is irrelevant here and isn’t what’s causing the warning.

    We believe the root cause is that your USG FLEX 100 doesn’t yet trust the new chain — GoDaddy TLS Intermediate CA DV R1v1 and its root. Without the full chain imported, the path is incomplete and the browser flags it untrusted.

    Please follow the steps here to address the issue:

    • Download the new intermediate and root certificates from GoDaddy, import both under Configuration > Object > Certificate > Trusted Certificates.
    • Build a .pfx with only your leaf certificate + private key (no intermediate bundled — USG rejects PFX files containing intermediates). Import under My Certificates.
    • Go to Configuration > System > WWW, set it as your Server Certificate, and Apply.

    One more thing to check: if you (or your team) access the WebGUI via the IP address (e.g. 192.168.x.x) instead of your domain, you’ll still see “Not secure” even with a perfectly valid chain — the certificate is issued for your domain name only, not the IP, so browsers will always flag a name mismatch on IP access. Always use the domain name to get the trusted padlock.

    Note: We verified this exact scenario end-to-end with a test certificate: once the leaf, all intermediates, and the root are imported, the connection is fully trusted — no ClientAuth required.

    Zyxel_Judy