Custom domain stuck on "Issuing TLS certificate"
Hi, I am moving my production site over to Railway from Vercel and it has been down for almost 24 hours now with this issue. I have added custom domains to Vercel many times in the past and it hasn't ever taken more than like 10 min which is why I am concerned theres a bug. I have tried deleting and re-adding the domain.
Solution:Jump to solution
I know you've done this a lot before, but mind just doing this one last time 🙏
remove the
nouns.gg domain from Railway
remove the CNAME for nouns.gg from Namecheap
then...31 Replies
Project ID:
6b3f7e42-b250-4b53-8639-abb14c79ab8b6b3f7e42-b250-4b53-8639-abb14c79ab8b
could you try removing it both from Railway and from your name server before re-adding it?
I've done that a few times already, just did it again how long should I wait to determine if its broke or not?
It can take up to 2 days to work, but it typically finishes within a few minutes
Somehow trying to add the root level domain to my production deployment took down my subdomain on my dev deployment. I readded it to the dev enviroment and it went live in 5 min. Still nothing on the root level domain which was added before it, could there be an issue there or do root level ones typically take longer than subdomains?
There isn't a difference in speed from what I know
I'm thinking the job for issuing the TLS certificate expired and needs to be restarted, although as you said you've tried doing that before and it didn't work so I'm very puzzled
When doing this, are you sure you had it removed from both Railway and from Namecheap before reattempting to add it?
Railway said there was nothing for that record set yet
I had readded it a few times and sometimes it said wrong value and specifically that time it said there was nothing there
im getting this now which seems like progress
tho, when that privacy error showed up on beta.nouns.gg was after it said TLS was issued successfully
still says its issuing for root level one
keeps going back and forth between this and this
this is interesting 🤔
what did you change?
nothing since this
Solution
I know you've done this a lot before, but mind just doing this one last time 🙏
remove the
nouns.gg domain from Railway
remove the CNAME for nouns.gg from Namecheap
then
add the nouns.gg domain back to Railway
add the CNAME for nouns.gg back to namecheap under the value Railway will provide
the reason I'm so set on doing this is because I don't believe I've ever encountered an issue like this where removing it from the nameserver and from Railway and adding it back didn't solve the issueI will once the DNS properly propagates, taking a while
waiting for it to say "no value set"
unless you think its fine to proceed
It's probably best you proceed with adding the CNAME on Namecheap
ok it finally updated anyways
oh okay, neat
fantastic, now we just wait
now it worked :/
maybe its because I waited longer than usual this time?
Awesome!!
thanks for the help, still has a privacy error but hopefully that resolves in a sec
no problem 🙂
and yea that should go away in time