Project: omega-measure (production environment)

Service: omega-measure

Custom Domain ID: 771cdd70-afa8-4b8b-ae52-b137f89153b0

Domain: estimate.omegaroofingllc.com

Current State

The custom domain has been stuck in an incomplete verification and certificate provisioning state for approximately 28 days.

Domain Configuration Status:

• syncStatus: ACTIVE
• verified: false
• certificateStatus: CERTIFICATE_STATUS_TYPE_ISSUING
• updatedAt: 2026-07-23T05:02:42.260+00:00 (no changes since July 23)

DNS Configuration (verified correct):

• Required CNAME record: estimate.omegaroofingllc.com → juyfyqbg.up.railway.app ✓ (matches Railway's requirement, publicly propagated, verified through multiple resolvers and authoritative nameserver)
• Required TXT ownership-verification record: ✓ (present and publicly propagated)

Certificate Issue:

• Current certificate served: *.up.railway.app (Railway's generic fallback)
• Domain in certificate SAN: absent (estimate.omegaroofingllc.com is not listed)
• HTTPS connection header: x-railway-fallback: true
• Result: HTTPS requests fail hostname validation

Application Status:

• Service health: good (application responds normally through the Railway-provided domain omega-measure-production.up.railway.app)
• Only issue is the custom domain certificate

Problem

The domain is in a deadlock state:

1. DNS records are correct and detected (syncStatus: ACTIVE)
2. But ownership verification never completed (verified: false)
3. Certificate issuance is blocked, showing CERTIFICATE_STATUS_TYPE_ISSUING for 28 days
4. The "retry certificate" button is unavailable because Railway considers the domain status "in progress" rather than "failed"
5. Background certificate provisioning job has not re-run or updated the domain since July 23

This appears to be either a stale job, a crash in the verification flow that left the domain record in an incomplete state, or a race condition where the DNS verification passed but the verified flag was never set to true.

Request

Please investigate and repair the stuck custom-domain verification and certificate provisioning state. Specifically:

• Verify whether the DNS/CNAME/TXT records were successfully validated on Railway's side
• If validation passed, update the domain's verified flag to true in the backend
• Re-trigger the certificate provisioning/Let's Encrypt request for this domain
• Confirm that the custom domain certificate has been issued and is being served