a month ago
My production service exposes two listeners:
Website on port 8080
API on port 3001
mappingwithmelanin.com provisions SSL correctly and loads over HTTPS.
api.melaninmaps.com has:
Valid CNAME
Valid TXT verification
DNS propagation confirmed globally
Healthy deployment
The application is working correctly.
The deployment logs show:
Listening on port 8080 — API on 3001
The Railway-generated domain loads correctly:
https://api-server-production-a991.up.railway.app
However, api.melaninmaps.com continues presenting the Railway wildcard certificate (*.up.railway.app) instead of provisioning its own Let's Encrypt certificate, resulting in a certificate name mismatch in browsers.
Could someone please check whether the SSL certificate provisioning for api.melaninmaps.com is stuck or failed after DNS verification completed? If possible, could you refresh or reissue the certificate for this custom domain?
I have already removed and re-added the custom domain inside Railway after DNS verification completed, but the certificate is still serving the Railway wildcard certificate.
Thank you!
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open 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.