2 hours ago
Hello Railway Support,
I'm experiencing an SSL certificate issue with my custom domains.
I have both:
- flowsynai.com
- *.flowsynai.com
configured on Railway.
The wildcard domain appears to be working correctly, but the root domain (flowsynai.com) is presenting a certificate mismatch error. It looks like the wildcard certificate is being served, but it does not properly match the apex domain.
As a result, accessing https://flowsynai.com returns an SSL certificate error, while wildcard subdomains continue to work.
Could you please investigate the certificate provisioning and ensure that flowsynai.com is included correctly alongside the wildcard domain?
Thank you.
13 Replies
2 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 hours ago
2 hours ago
Hi! I just tested the root domain (https://flowsynai.com) and it appears to be loading securely without any SSL errors now. Could you try clearing your browser cache or opening it in an Incognito window to check if it's working on your end too, or hard refresh the browser, it should work
.
2 hours ago
its been going on and off
simplitech-code
its been going on and off
2 hours ago
An intermittent SSL issue usually points to a DNS configuration conflict. If you are using Cloudflare, try switching your SSL/TLS encryption mode from Full (Strict) to Full, as strict mode often blocks Railway's background renewal checks.
Also, double-check your DNS dashboard to ensure you don't have conflicting A and CNAME records both trying to point to your root domain, and verify that the _railway-verify TXT record from Railway is properly added.
that should fix it
2 hours ago
This is all i have set
2 hours ago
nice, all you are missing is the required domain verification record for the root domain. To stabilize the SSL certificate, go to your Railway dashboard under your custom domain settings, find the TXT record named _railway-verify, and add it to this DNS dashboard. Once that record is added alongside your existing CNAMEs, Railway will be able to consistently validate and lock in your root SSL certificate.
thats the fix
2 hours ago
This how i set everything still the ssl comes up frequently i will still watch for some days
2 hours ago
The root cause of the unstable SSL is that Railway requires two distinct verification tokens with the same name (_railway-verify), which are currently conflicting in your Namecheap DNS panel. To stabilize this permanently, you need to add both TXT records correctly: add one TXT record with the Host set to _railway-verify using the value from your root domain dashboard, and add a second TXT record with the Host set to _railway-verify.* using the value from your wildcard dashboard. This ensures Railway can validate both domains simultaneously and stops the certificate from dropping on and off.
dev-charles254
The root cause of the unstable SSL is that Railway requires two distinct verification tokens with the same name (_railway-verify), which are currently conflicting in your Namecheap DNS panel. To stabilize this permanently, you need to add both TXT records correctly: add one TXT record with the Host set to _railway-verify using the value from your root domain dashboard, and add a second TXT record with the Host set to _railway-verify.* using the value from your wildcard dashboard. This ensures Railway can validate both domains simultaneously and stops the certificate from dropping on and off.
2 hours ago
Did you check screenshoots i attached
simplitech-code
Did you check screenshoots i attached
an hour ago
I checked, and your problem is actually fixed. Running a ** curl -vI .... ** on your domain returns a healthy 200 OK. If it’s still showing an error for you, it’s just your browser cache, so try testing it in an incognito window. you are good now
dev-charles254
I checked, and your problem is actually fixed. Running a ** curl -vI .... ** on your domain returns a healthy 200 OK. If it’s still showing an error for you, it’s just your browser cache, so try testing it in an incognito window. you are good now
an hour ago
Okay I will wait for few days again and see if this is totally fixed
