a month ago
I've been unable to get SSL working for my custom domain mach-hrm.com for 4-5 days now.
What I've done:
- Domain DNS is correctly configured (CNAME @ → feywlfzf.up.railway.app, TXT _railway-verify both show green ✅ in Railway)
- Removed the domain from Bluehost hosting (it was previously set up as a hosted site there, which I've now deleted)
- Deleted and re-added the custom domain in Railway multiple times
- Updated the CNAME each time to match the new Railway subdomain
Current error shown in Railway: "Failed to issue TLS certificate. Let's Encrypt rate limit reached."
The app itself works fine at hrm-frontend-production.up.railway.app — it's only the custom domain SSL that won't provision.
Could you please manually trigger a certificate re-issuance or check if there's a rate limit block on mach-hrm.com? I'm on the Pro plan.
Pinned Solution
a month ago
The rate limit is based on a rolling 7-day (a week, as mentioned above) window. Try removing the domain from Railway and add it back after ~10-15 mins after the window has passed.
4 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’ll need to wait for a week for Let’s Encrypt’s rate limit to be lifted for that hostname. There isn’t anything Railway can do about this.
0x5b62656e5d
You’ll need to wait for a week for Let’s Encrypt’s rate limit to be lifted for that hostname. There isn’t anything Railway can do about this.
a month ago
Like how mnay days, today is day 3 now
a month ago
The rate limit is based on a rolling 7-day (a week, as mentioned above) window. Try removing the domain from Railway and add it back after ~10-15 mins after the window has passed.
0x5b62656e5d
The rate limit is based on a rolling 7-day (a week, as mentioned above) window. Try removing the domain from Railway and add it back after ~10-15 mins after the window has passed.
a month ago
Thanks
Status changed to Solved 0x5b62656e5d • 16 days ago