Custom domain www.pklandscapingmn.com failing to persist in service config
egartei5
HOBBYOP

15 days ago

Custom domain www.pklandscapingmn.com failing to persist in service configHello Railway team,

My custom domain (www.pklandscapingmn.com) keeps failing to persist / disappearing from my service settings.

I have verified that my repository's railway.Hello Railway team,

My custom domain (www.pklandscapingmn.com) keeps failing to persist / disappearing from my service settings.

I have verified that my repository's railway.json file does not contain any networking or serviceDomains properties that would override the dashboard settings.

Service ID: 3147fef2-44e3-472b-ba5b-2b6d7836b638

Could you please assist in checking why thHello Railway team,

My custom domain (www.pklandscapingmn.com) keeps failing to persist / disappearing from my service settings.

I have verified that my repository's railway.json file does not contain any networking or serviceDomains properties that would override the dashboard settings.

Service ID: 3147fef2-44e3-472b-ba5b-2b6d7836b638

Could you please assist in checking why this domain configuration is not persisting in the backend?is domain configuration is not persisting in the backend?json file does not contain any networking or serviceDomains properties that would override the dashboard settingsHello Railway team,

My custom domain (www.pklandscapingmn.com) keeps failing to persist / disappearing from my service settings.

I have verified that my repository's railway.json file does not contain any networking or serviceDomains properties that would override the dashboard settings.

Service ID: 3147fef2-44e3-472b-ba5b-2b6d7836b638

Could you please assist in checking why this domain configuration is not persisting in the backend?.

Service ID: 3147fef2-44e3-472b-ba5b-2b6d7836b638

Could you please assist in checking why this domain configuration is not persisting in the backend?

Solved

3 Replies

Railway
BOT

15 days ago

The domain www.pklandscapingmn.com is currently attached to your service, with its CNAME correctly propagated, a valid TLS certificate, and verification complete. There are no pending staged changes that would remove it. If the dashboard view appears stale, try a hard refresh of the page or switching to another environment and back.


Status changed to Awaiting User Response Railway 15 days ago


Railway

The domain `www.pklandscapingmn.com` is currently attached to your service, with its CNAME correctly propagated, a valid TLS certificate, and verification complete. There are no pending staged changes that would remove it. If the dashboard view appears stale, try a hard refresh of the page or switching to another environment and back.

egartei5
HOBBYOP

14 days ago

The issue isn't the current state, but that the custom domain configuration disappears from the dashboard periodically. I have verified my railway.json has no domain overrides. Could a human engineer please look into why the backend is failing to persist this setting


Status changed to Awaiting Railway Response Railway 14 days ago


chandrika
EMPLOYEE

14 days ago

We understand the concern is about intermittent disappearances, not the current state. To confirm what the data shows right now: the domain is attached, DNS is propagated, the certificate is valid, and there are no staged changes queued that would remove it. On the railway.json angle, config-as-code only covers build and deploy settings, not domain/networking configuration, so it cannot be the cause even if a property were present. If you do catch the domain in its "disappeared" state, a screenshot of the service's networking section at that moment would help us confirm whether this is a display issue or an actual backend removal.


Status changed to Awaiting User Response Railway 14 days ago


Railway
BOT

6 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 6 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...