#Custom domain cert not provisioning — stuck on *.up.railway.app wildcard

6 messages · Page 1 of 1 (latest)

lean hollow
#

Project: strong-mindfulness (ID: 167d341a-aebf-449f-881a-c6d47dfa853d)
Service: STIM (ID: 275b01ba-5778-49a7-bc23-e740c272a3f3)
Environment: production (e415ff7a-dbec-4e2a-a480-f491292aa4cf)
Custom domain: stim.bonetti.tech
Custom domain ID: 010003fe-cde3-4e29-907d-058f32cfe035

Issue: The custom domain stim.bonetti.tech has cnameCheck: VALID (CNAME → stim-production.up.railway.app) but Railway is still serving the *.up.railway.app wildcard certificate instead of provisioning a cert for stim.bonetti.tech. This has been the case for 12+ hours. I have tried deleting and re-adding the custom domain multiple times and triggering redeployments — cert provisioning never fires. The app is healthy and accessible via the internal .up.railway.app domain.

Please help.

devout mistBOT
#

Is this about a specific service? Linking one helps us understand your setup.

drowsy ridge
lean hollow
#

Yes — here's the full context:

Service link: https://railway.com/project/167d341a-aebf-449f-881a-c6d47dfa853d/service/275b01ba-5778-49a7-bc23-e740c272a3f3

Custom domain: stim.bonetti.tech
Custom domain ID: 010003fe-cde3-4e29-907d-058f32cfe035
CNAME status: VALID (pointing to stim-production.up.railway.app)

The CNAME has been valid for 12+ hours but Railway has not provisioned a TLS certificate for stim.bonetti.tech. The service is still serving the *.up.railway.app wildcard cert when accessed via the custom domain. I've tried deleting and re-adding the custom domain multiple times and triggering redeployments — cert provisioning never fires. The app itself is healthy via the internal domain.

drowsy ridge
lean hollow
#

The CNAME for stim.bonetti.tech points to stim-production.up.railway.app and the Railway dashboard shows cnameCheck: VALID. There are currently no TXT records on that subdomain. Railway is not showing any required TXT records in the dashboard for this domain — the domain settings page only shows the CNAME requirement, which is already satisfied.

Could you confirm what TXT record is needed and what value it should have? I can add it immediately.