Custom domain pointing Stuck at "Issuing TLS certificate" after adding @ CNAME record. Please help!
I've added the @ CNAME record on domain DNS and the root domain is reflecting the propagation - when you type the domain name, the website opens but without SSL. The status of the custom domain is stuck on "Issuing TLS certificate" for almost 48 hours.
Do I need to add any extra DNS entries or CNAME to get the SSL certificate? as the @ is added in CNAME, i'm not sure the following is applicable?
found this in documentation - https://docs.railway.app/deploy/exposing-your-app#wildcard-domains
Ensure that the CNAME record for authorize.railwaydns.net is not proxied by your provider (eg: Cloudflare). This is required for the verification process to work.
Wildcards can be used for any subdomain level (eg: *.yourdomain.com or *.subdomain.yourdomain.com).
In order to use Wildcard Domains, you must add two CNAME records, one for the wildcard domain, and one for the _acme-challenge. The _acme-challenge CNAME is required for Railway to issue the SSL Certificate for your domain.
Please help in resolving
12 Replies
Project ID:
6bd0a3f2-4a34-4935-9e84-c16c6b98dd6eProject ID - 6bd0a3f2-4a34-4935-9e84-c16c6b98dd6e
you aren't using a wildcard domain, so that documentation is irrelevant
your domain does actually seem to be setup correctly from what I can dig
it's currently the weekend and the team doesn't work on the weekends, so keep me updated and if an SSL cert isn't issued come Monday I will flag the team Monday for you
thanks
so let me know if anything changes by monday
sure chief
@Brody it is not issuing SSL.. please help!
no need for the ping #🛂｜readme #5
it's not currently work hours for a good chunk of the team, but I will flag them and they will help when they are available
Thread has been flagged to Railway team by @Brody.
thanks
Hey, can you delete the domain and re-add it to the service again?
I had the same issue and deleting and re-adding the domain like mentioned above helped
sure.. i'll try .. thanks