Your root domain godlyresponses.org is added to Railway but the required CNAME record pointing to 2t4s7ekq.up.railway.app is not in place yet, which is why the SSL certificate is stuck on validation. Your DNS provider (ICEdns) does not appear to support CNAME flattening at the root (@), which is required for apex domains on Railway since we don't publish a static IP for A records. You can either switch your domain's nameservers to a provider that supports CNAME flattening (e.g. Cloudflare), or use www.godlyresponses.org as your primary domain instead. Also note that the Trial plan is limited to 1 custom domain, so you cannot add both godlyresponses.org and www.godlyresponses.org as separate custom domains at this time.

I removed the godlyresponses.org and changed it to www.godlyresponses.org but it's still givng me ssl error

Re-adding the domain as www.godlyresponses.org generated a new CNAME target. Your current CNAME still points to 2t4s7ekq.up.railway.app, but the required target is now n97h0lad.up.railway.app - update that at your DNS provider. You also need a TXT verification record, which you can find on the domain's settings page in your Railway dashboard alongside the CNAME target. Once both the updated CNAME and the TXT record propagate, the SSL certificate will issue automatically.

It's updated to www CNAME 14400

n97h0lad.up.railway.app and _railway-verify TXT 900

"railway-verify=31246cee6066aa79baee01a99eac28f402af50bd5e88593f185be854931acc8b"

but still showing as insecure.

Also they only let me do the www CNAM not @ - is that ok? I changed my railway to be www.godlyresponses.org

Also still giving me The train has not arrived at the station.

Please check your network settings to confirm that your domain has provisioned.

If you are a visitor, please let the owner know you're stuck at the station.

Request ID:

Even though the app is working fine on local and deployed fine.

Your CNAME is correct and propagated, but the TXT verification record is at the wrong hostname. It currently resolves at _railway-verify.godlyresponses.org, but since your custom domain is www.godlyresponses.org, Railway needs it at _railway-verify.www.godlyresponses.org. In your DNS provider, change the TXT record name from _railway-verify to _railway-verify.www and the certificate will issue once it propagates.

I updated the txt to _railway-verify.www TXT 900

"railway-verify=31246cee6066aa79baee01a99eac28f402af50bd5e88593f185be854931acc8b" what about this issue with the app itself giving the train has not entered the station - is that because of the certificate?

Yes, using only www for the CNAME is fine since your custom domain is www.godlyresponses.org. Your TXT record update worked, the domain is now verified, and the SSL certificate has issued successfully. The "train has not arrived" message was caused by the certificate not being in place yet. Everything is routing correctly now, so www.godlyresponses.org should be serving your app over HTTPS.