Would you be willing to provide the domain you’re trying to add?

can u share the domain name

This is likely just the normal certificate issuance window unless it has already been stuck for more than an hour after Railway shows the DNS records as valid.

Railway issues the HTTPS certificate automatically after the custom domain is correctly configured, but it is not instant. Keep both Railway-provided records in Strato exactly as shown:

• the CNAME record pointing to the Railway service domain
• the TXT verification record

Then wait up to about 1 hour for TLS issuance. DNS propagation itself can take longer, sometimes up to 72 hours.

A couple of checks:

1. If this is a subdomain like www.example.com or app.example.com, it should have the Railway CNAME plus the Railway TXT. Remove conflicting A or AAAA records for that same host.
2. If this is the root/apex domain like example.com, Railway does not support static A records. The DNS provider must support CNAME flattening / ALIAS / ANAME. If Strato does not support that for the root domain, use a www subdomain with a CNAME, or move DNS to a provider like Cloudflare that supports apex CNAME flattening.
3. In Railway, wait until the DNS status is valid first; the certificate status can remain “Issuing TLS” briefly after that.

If it is still stuck more than an hour after DNS is valid, remove the custom domain from Railway, remove the old DNS records at Strato, add the custom domain again in Railway, then add the newly generated CNAME/TXT records.

The domain name is www.psaportaal.nl

And it has been more than 1 hour

i can also access ur site!

You site is accessible

but it is nottt secured

it is showing secured for us

Is this in an incognito window? Try accessing it from a different device.

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.