2 months ago
Custom domain hr.yvane.ru has been stuck on "Waiting for DNS update" for 6+ hours. SSL certificate is not being issued.
DNS records (verified on authoritative NS ns1.spaceweb.ru and 1.1.1.1):
- CNAME hr → ddy9e4as.up.railway.app
- TXT _railway-verify.hr → railway-verify=railway-verify=39f68d8ca80948b189d8208fee42ced37cb739317af92ed554b71b39b3abfc22
- TXT _railway-verify (root) → same value (added as extra attempt)
HTTP on port 80 responds with 301 redirect to HTTPS.
Domain was deleted and re-added 5+ times via CLI — no change.
Trial plan, only 1 custom domain active on the service.
SSL still shows CN=*.up.railway.app.
Could you please check what's blocking Let's Encrypt certificate issuance on your end?
1 Replies
2 months ago
Your CNAME record points to ddy9e4as.up.railway.app, but our system expects it to point to qt11xzdo.up.railway.app (this likely changed after re-adding the domain). Additionally, your TXT verification value contains a doubled prefix: railway-verify=railway-verify=39f6... when it should be just railway-verify=39f6.... Update the CNAME target to qt11xzdo.up.railway.app and fix the TXT record at _railway-verify.hr.yvane.ru to remove the extra railway-verify= prefix, then the certificate should issue once both propagate.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 1 month ago