2 months ago
the cert issued is for *.up.railway.app, not plutocrat.world. Railway is serving the wildcard Railway cert instead of issuing a custom one for my domain. The site works but browsers show it as insecure because the cert doesn't match the domain.
6 Replies
2 months ago
Your CNAME record for plutocrat.world is pointing to w385wckm.up.railway.app, but our system expects it to point to y8o6u8kg.up.railway.app. This mismatch is preventing the SSL certificate from being issued for your domain. Please update the CNAME record at your DNS provider to point to y8o6u8kg.up.railway.app, and the certificate should issue once the updated record propagates.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
It is updated to y8o6u8kg.up.railway.app , I think you may have cached an earlier attempt
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your CNAME is now correctly pointing to the expected target and public DNS confirms this, but our internal system still shows the old value. The certificate is currently in the process of issuing. This should resolve shortly as our system picks up the updated DNS, but if the certificate remains stuck, we can look into refreshing it on our end.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
Your CNAME is now correctly pointing to the expected target and public DNS confirms this, but our internal system still shows the old value. The certificate is currently in the process of issuing. This should resolve shortly as our system picks up the updated DNS, but if the certificate remains stuck, we can look into refreshing it on our end.
2 months ago
Since it has been stuck for quite some time, let's try a refresh
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved chvolk • about 2 months ago
2 months ago
Can we reopen this? Same error
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey,
Sorry about that. We have rolled out a fix for this. You should be all set now.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months 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 • about 2 months ago