Skip to content
Certificate Authority is validating challenges
ecommerce101
OP

a month ago

I am getting this: Certificate Authority is validating challenges

domain is with name cheap but i am managing its DNS at hostinger

Solved

9 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

Your DNS at Hostinger is set up correctly: the CNAME points to the target we expect, domain ownership is verified, and the certificate authority's challenge request reaches your service. Managing DNS at Hostinger while the domain is registered at Namecheap is fine, and no DNS records need to change.

The "Try Again" retry button only appears in the domain's networking settings once a certificate attempt has failed, so it is not available while the domain shows this validating state.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway

Your DNS at Hostinger is set up correctly: the CNAME points to the target we expect, domain ownership is verified, and the certificate authority's challenge request reaches your service. Managing DNS at Hostinger while the domain is registered at Namecheap is fine, and no DNS records need to change. The "Try Again" retry button only appears in the domain's networking settings once a certificate attempt has failed, so it is not available while the domain shows this validating state.

ecommerce101
OP

a month ago

The certificate has been validating for over two hours. DNS and ownership are verified, but HTTPS still returns ERR_CERT_COMMON_NAME_INVALID. Could you investigate the pending certificate request for giftflow.ecommerce101.ca?


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

The ERR_CERT_COMMON_NAME_INVALID error means a certificate for your domain has not been issued yet, so browsers are shown a default certificate that doesn't cover your hostname. The request is still in the certificate authority's validation stage, which normally completes well within two hours.

Your records at Hostinger are correct as they stand now and ownership is verified, but the certificate authority checks from its own network locations, and a resolver there can still hold an older answer for a while after a DNS change. Please don't remove and re-add the domain, as that would generate a new CNAME target and verification record and you would have to redo your DNS.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway

The ERR_CERT_COMMON_NAME_INVALID error means a certificate for your domain has not been issued yet, so browsers are shown a default certificate that doesn't cover your hostname. The request is still in the certificate authority's validation stage, which normally completes well within two hours. Your records at Hostinger are correct as they stand now and ownership is verified, but the certificate authority checks from its own network locations, and a resolver there can still hold an older answer for a while after a DNS change. Please don't remove and re-add the domain, as that would generate a new CNAME target and verification record and you would have to redo your DNS.

ecommerce101
OP

a month ago

Understood, Thankyou


Status changed to Awaiting Railway Response Railway • about 1 month ago


sam-a
EMPLOYEE

a month ago

The certificate still hasn't issued. Your domain is still in the certificate authority's validation stage, which is why HTTPS shows ERR_CERT_COMMON_NAME_INVALID. Your DNS record at Hostinger is still correct and ownership is still verified, so there's nothing for you to change.

Please leave the domain as it is. Removing and re-adding it would create a new CNAME target and you'd have to update your DNS again.


Status changed to Awaiting User Response Railway • about 1 month ago


ecommerce101
OP

a month ago

Failed to issue TLS certificate

Try Again

An internal error occurred. Please retry or contact support.

this is what i am getting


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

That banner means the certificate order failed: when the certificate authority checked your domain, at least one of its network locations still got an older DNS answer and couldn't reach the challenge on your service. A failed order can't recover by waiting, so it needs a fresh attempt.

The "Try Again" button on that banner, in the domain's row under your service's Settings > Networking, starts a new certificate order. Your records at Hostinger are correct and ownership is verified, so a fresh attempt is what this calls for. Please don't remove and re-add the domain, as that would give you a new CNAME target and you'd have to redo your DNS.


Status changed to Awaiting User Response Railway • about 1 month ago


Anonymous

a month ago

If I were you, I'd delete it and try again - sometimes things get funky or extra spaces are introduced from a copy/paste. Just my two cents


Status changed to Awaiting Railway Response Railway • about 1 month ago


a month ago

The certificate for your domain has now been issued, so HTTPS should load without the ERR_CERT_COMMON_NAME_INVALID error. There's no need to remove and re-add the domain, and doing so would give you a new CNAME target and verification record to set up again.

If your browser still shows the old error, a hard refresh or a new private window will pick up the new certificate.


Status changed to Awaiting User Response Railway • about 1 month ago


Status changed to Solved brody • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...