a month ago
there's an issue with 2 services that dns doesn't update and thus certificate isn't being issued
Attachments
Pinned Solution
a month ago
You need to add a TXT record to _railway-verify.www.maplesidemfg.ca. Also, double check if the required records for api.maplesidemfg.ca are up to date.
Lastly, it may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
12 Replies
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
a month ago
You need to add a TXT record to _railway-verify.www.maplesidemfg.ca. Also, double check if the required records for api.maplesidemfg.ca are up to date.
Lastly, it may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
a month ago
is that correct or should that be changed to _railway-verify.www.maplesidemfg.ca ? The host I mean
Attachments
0x5b62656e5d
You need to add a TXT record to `_railway-verify.www.maplesidemfg.ca`. Also, double check if the required records for `api.maplesidemfg.ca` are up to date. Lastly, it may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
a month ago
is that correct or should that be changed to _railway-verify.www.maplesidemfg.ca ? The host I mean
Status changed to Solved 0x5b62656e5d • about 1 month ago
0x5b62656e5d
The record should be on `_railway-verify.www`.
a month ago
we have this record for api added but railway still didn't process it. can you force it somehow please?
Attachments
Status changed to Awaiting Conductor Response Railway • about 1 month ago
a month ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
Status changed to Awaiting User Response Railway • about 1 month ago
0x5b62656e5d
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
a month ago
it's since yesterday's morning so I don't think that would be the case. I tried re-adding multiple times already
Status changed to Awaiting Conductor Response Railway • about 1 month ago
Status changed to Awaiting User Response Railway • about 1 month ago
0x5b62656e5d
Try deleting the DNS records from your DNS provider as well.
a month ago
I tried doing that multiple times yesterday. Is that possible to flush it somehow from your side? Force-refresh or something, please
Status changed to Awaiting Conductor Response Railway • about 1 month ago
0x5b62656e5d
Try deleting the DNS records from your DNS provider as well.
a month ago
hello! still issue isn't resolved
a month ago
Remove the domain from Railway completely
Delete all related DNS records from your DNS provider (CNAME + TXT for that subdomain)
Wait 10–15 minutes
Re-add the domain in Railway — it will give you fresh CNAME/TXT values
Add both records to your DNS provider
Wait for propagation (use dig to confirm they resolve correctly)
Railway polls every few minutes once records are live
7 days ago
that's resolved now, thanks everyone!