invalid sfo region config blocking SSL provisioning
austinagents
FREEOP

an hour ago

Project ID: 4419485f-4b00-4711-8ed5-bd475206b2c1

Service ID: 7ed40169-864b-4f90-9f8e-fcf744212558

Issue:
My custom domain SSL provisioning is stuck and Chrome shows:
NET::ERR_CERT_COMMON_NAME_INVALID

Railway networking shows:
“Waiting for DNS update”

DNS is already propagated globally:

An internal Railway agent identified an invalid sfo region key inmultiRegionConfig blocking all updates and SSL provisioning.

Attempting to patch/update the service fails because the invalid region config cannot be removed from the service state.

Can a Railway staff member please clear/remove the invalid sfo region entry from this service so SSL provisioning can complete?

Thank you.

$10 Bounty

2 Replies

Status changed to Open Railway about 1 hour ago


austinagents
FREEOP

an hour ago

Additional context from Railway Agent:

The issue appears to be a platform-side config corruption involving an invalid/deprecated sfo region key in multiRegionConfig.

Attempts to update the service region fail validation because the invalid sfo enum cannot be removed through the UI/API.

Project ID:
4419485f-4b00-4711-8ed5-bd475206b2c1

Service ID:
7ed40169-864b-4f90-9f8e-fcf744212558

This appears to be blocking:

  • service updates

  • SSL issuance

  • custom domain validation

DNS/TXT verification is already configured and globally propagated.

If someone can check this I’d appreciate it. @railway-support @moderator


If you're adding a www domain, make sure the TXT record exists on _railway-verify.www. If you're adding your root domain, you should be adding a CNAME record to your root domain and a TXT record to _railway-verify. You should not be using A records.

If your DNS provider does not support adding CNAME records on root domains, I'd recommend switching to Cloudflare's DNS service, as they support CNAME flattening (using CNAME records on root domains).

https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/


Welcome!

Sign in to your Railway account to join the conversation.

Loading...