24 days ago
I have a custom domain insider-bagger.com (purchased through Railway) connected to my edgar-v2-web service. The SSL certificate has been invalid for several days despite multiple attempts to fix it.
Issue:
- Domain shows as invalid certificate when accessed via HTTPS
- Browser shows "connection is not secure"
- Service domain is set to port 80, but the domain still tries to use port 443
- Manually changed port to 80 in settings, but it reverts or doesn't take effect
What I've tried:
- Changed service domain port from 443 to 80 and the other way around
- Removed and re-added the domain
- Cleared browser cache and tried incognito window
- Deployed the service multiple times
Current setup:
- Service: edgar-v2-web (React frontend)
- Domain: insider-bagger.com (Railway-purchased)
- Port: 80
- Question: Why is the SSL certificate not provisioning? Is there a DNS verification issue or a bug with Railway-purchased domains?
9 Replies
Status changed to Open Railway • 24 days ago
24 days ago
Using 80/443 will not affect the state of the certificate. I'd try accessing the site from an incognito window or a different device. If that still doesn't work, try removing the domain from Railway, wait for ~10-15 mins, then add the domain back.
24 days ago
Additionally, make sure the port your URL is mapped to is the same port your application is listening to.
24 days ago
This looks like a DNS issue rather than a Railway port or React app issue.
Your domain currently resolves to: 151.101.2.15
And from the checks you shared, there doesn’t seem to be a visible TXT verification record or CNAME/routing record for Railway. The authoritative nameserver also shows as ns1.name.com.
That means Railway probably can’t verify the domain or provision the SSL cert yet, because the required DNS records aren’t being served publicly.
I wouldn’t worry too much about the port 80 vs 443 part. HTTPS will always hit 443 publicly. The port setting in Railway is just the internal port Railway forwards traffic to after TLS termination, so setting the service to port 80 is fine if that’s what the app listens on.
I’d check the DNS records for the domain and remove the A record pointing to 151.101.2.15 if it’s stale. Then make sure Railway’s required TXT verification record and routing record are present.
Since this was purchased through Railway, it may be worth asking Railway support/mods to check whether the managed DNS got stuck or wasn’t created correctly.
moeamine
This looks like a DNS issue rather than a Railway port or React app issue. Your domain currently resolves to: 151.101.2.15 And from the checks you shared, there doesn’t seem to be a visible TXT verification record or CNAME/routing record for Railway. The authoritative nameserver also shows as [ns1.name.com](http://ns1.name.com). That means Railway probably can’t verify the domain or provision the SSL cert yet, because the required DNS records aren’t being served publicly. I wouldn’t worry too much about the port 80 vs 443 part. HTTPS will always hit 443 publicly. The port setting in Railway is just the internal port Railway forwards traffic to after TLS termination, so setting the service to port 80 is fine if that’s what the app listens on. I’d check the DNS records for the domain and remove the A record pointing to 151.101.2.15 if it’s stale. Then make sure Railway’s required TXT verification record and routing record are present. Since this was purchased through Railway, it may be worth asking Railway support/mods to check whether the managed DNS got stuck or wasn’t created correctly.
23 days ago
From what I undersatnd, name.com proxies CNAME records similar to Cloudflare. It dynamically routes CNAME to an IP address.
22 days ago
according to documentation Railway Domains | Railway Docs
railway.com should handle my dns txt
its not happening , what can i do ?
guymalka
according to documentation [Railway Domains | Railway Docs](https://docs.railway.com/networking/domains/railway-domains) [railway.com](http://railway.com) should handle my dns txt its not happening , what can i do ?
22 days ago
(Your TXT record is already added)
22 days ago
It seems like the certificate doesn't have any issues. Just make sure you're mapping the correct port to your custom domain.
Attachments
22 days ago
im using domain i bought from railway.com accoring to docs Railway Domains | Railway Docs i dont need to do anything regards to txt dns
the website is up right now , and certificate issue still relevant
Attachments
22 days ago
Status changed to Closed brody • 22 days ago