# Why might HTTPS fail shortly after I connect a custom hostname?

Canonical URL: https://help.iagenify.com/faqs/hosting/why-might-https-fail-shortly-after-i-connect-a-custom-hostname

[← Back to Hosting FAQs](https://help.iagenify.com/faqs/hosting)

HELP CENTER · FAQ Hosting 2 min read
# Why might HTTPS fail shortly after I connect a custom hostname?
The hostname may be attached before its certificate is ready. Check the hosting status for certificate progress and verify DNS and hostname association before treating the deployment as broken.
IaGenify
Hosting

## Separate deployment health from certificate readiness
A successful deployment and a usable HTTPS endpoint are related but distinct checks. The application can be deployed while certificate issuance or validation for a newly connected hostname is still pending. During that interval, a browser may fail the secure connection even though the deployment itself completed.
Confirm that the exact hostname is associated with the intended project and that its DNS reaches the configured destination. Test the root name and www separately if both are used. A certificate check for one name does not confirm readiness for another hostname.
## Wait for readiness, then test the exact URL
Review the certificate state shown for the host and allow its validation process to complete before repeatedly changing DNS or redeploying. If the status remains pending beyond the expected process, record the hostname and status details for support rather than guessing at the cause.
When the certificate becomes active, open the full HTTPS address in a fresh browser session and check the page and redirect behavior. If the error persists, compare the hostname, DNS target, and certificate name. Avoid telling visitors to bypass a certificate warning; it means the secure connection is not being verified. [← Back to Hosting FAQs](https://help.iagenify.com/faqs/hosting)