Custom domain SSL not provisioning
Anonymous
PROOP

a month ago

Project: 2ff96d41-a1fc-491c-bc58-12e8077e4585

Service: 23e548d5-d442-4e4e-b035-831803808f5b (dikla-backend)

Custom domain SSL stuck in pending state. Tested 3 different

hostnames over 90 min:

  • api.dikla.brndini.co.il (deleted)
  • dikla-api.brndini.co.il (deleted)
  • bot.brndini.co.il (deleted)

For each: DNS_RECORD_STATUS_PROPAGATED confirmed,

currentValue == requiredValue, no certificateErrorMessage,

but certificates array remained empty after 30+ min wait.

Could you investigate why SSL provisioning isn't completing?

Solved$20 Bounty

Pinned Solution

You need to add a TXT record to _railway-verify.<DOMAIN> where <DOMAIN> is the domain you're trying to add. You can access the content for the TXT record under verificationToken under status.

1 Replies

Railway
BOT

a month ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway about 1 month ago


You need to add a TXT record to _railway-verify.<DOMAIN> where <DOMAIN> is the domain you're trying to add. You can access the content for the TXT record under verificationToken under status.


Status changed to Solved 0x5b62656e5d 5 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...