Custom domain validation failing - certificate issuance blocked for extended period
remlass
PROOP

a month ago

Please, don't put it in public, I have already tried without success, just update the DNS checking it should work, it's urgent thanks!

Situation: HTTPS certificate validation is failing for the custom domain. The domain validation shows a warning indicator despite DNS records being correctly configured and propagated. Certificate issuance has been blocked for an extended period (72+ hours).

DNS Configuration Status:

  • CNAME record: properly configured and pointing to Railway endpoint ✓
  • Validation record: present in DNS zone ✓
  • DNS propagation: verified and confirmed across multiple checkers
  • CAA records: no blocking restrictions present
  • DNSSEC: configuration validated
  • Service: deployed and operational

Current Blockers:

  • Certificate remains in pending/validating state
  • Validation check shows warning status in dashboard
  • No automatic resolution after several weeks
  • Limited ability to make DNS changes for the next few hours

Request: Need Railway team to investigate the validation failure on the platform side and manually clear the certificate issuance block for this domain.

$20 Bounty

2 Replies

Railway
BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway about 1 month ago


What domain are you using? Make sure you added the TXT record on _railway-verify.<DOMAIN> where <DOMAIN> is the domain you're trying to add. If you're using the API, you can get the content for it from the verificationToken property under status.


a month ago

Hello,

First-party support here focuses on the Railway platform itself. For help with what you build and run on it (your application, code, framework, configuration, or DNS and domain setup), our community is the right place, where other Railway users will dig into exactly these.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...