SSL certificate to custom subdomain error
The domain has a proper SSL certificate, the subdomain too, but as long as I link my railway app to the custom subdomain, the SSL disappear.
I tried many configuration from the domain-owning platform side, but it seems the issue comes from railway. How long does it take to propagate a SSL when linking a new custom domain ?
13 Replies
Project ID:
9cb12826-e981-4783-98e6-6156ba8e7dad9cb12826-e981-4783-98e6-6156ba8e7dad
docs say up to 72 hours, but I've never seen it take that long
it's likely just a configuration mistake in the DNS, could you send me some screenshots? railway domains modal, your DNS settings for your domain, etc
I went to private messages to send you screenshots
let's not do that
send the images here please
#🛂｜readme says to not dm without permission
I just had a look at that domain - it looks like our initial issue attempts timed out (we try within a 6h window from creation, and then back off). I've manually triggered a retry.
What's the TTL you've set on the DNS record?
1h
Thank you for the retry
we'll increase the initial retry window - we plan on exposing those cert settings and the retry ability in the settings pane soon
I think* the cert should be issued now - you may need to restart the browser incase there are cached TLS session keys
Perfect !
Thank you very much for your reactivity !
It looks like I'm dealing with the same issue, is there a way to fork this thread for project: 1e5c78d0-ee30-4637-a2bd-3a1a5fde1c65
sorry about that, I'm still trying to find out why it failed all retry attempts. Should work now? We'll work on a fix and expose that cert state in the UI / along with giving users the ability to manually trigger a retry. Will also root cause why it took so long in this case.
Thanks
Yes, it looks like its properly provisioned now
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View