are both your services (the one making the call and leoums.dev) in the same railway project?

if yes , the most common cause of this exact error is trying to call a service's public domain from another railway service in the same project. railway's networking doesn't handle that well. the recommended solution is to use private networking instead; instead of calling https://leoums.dev/endpoint use http://[servicename].railway.internal:[PORT]/endpoint

it would explain why your rest client works (external call over public internet) but your deployed app doesn't (internal call that should use private network)

if they're in different projects, then this wouldn't apply and we'd need to look at other issues

for the "waiting for dns update" thing - that's usually just a display bug if the domain actually loads when you visit it. dns can take 24-72 hours to fully propagate

let me know if they're in the same project and i can give you more specific steps to try. don't want to suggest the wrong thing if your setup is different than what i'm thinking

my other service is making the call to leoums.dev and I switched it to call the private networking and it does solve that issue a bit but the other issue is that I really need it to call leoums.dev since that is the domain that i have linked to a email service client called "Resend" that will send out emails and calling the private network url wouldn't work with sending out emails.

so that dns error is your whole problem leoums.dev literally doesn't exist in dns right now, which is why railway can't verify it and why nothing can connect to it

here's what you need to do:

go to wherever you bought leoums.dev and check your dns settings. you need to add a cname record pointing to the railway url they gave you (should look like something.up.railway.app)

if you're trying to set up the root domain (just leoums.dev without www), some dns providers don't support that properly. easiest fix is to switch your nameservers to cloudflare (free) - they handle this correctly and railway works perfectly with them

once the dns is actually configured, wait like 10-30 mins, then both issues will be solved - the domain will work and your service will be able to call it for the resend emails

what dns provider are you using?

im using namecheap for everything. And that's strange that it doesn't work for you. It works for me. Can you prepend that with https://? So https://leoums.dev

also https://leoums.dev same error

ok let me try cloudflare then and get back to you when i get the chance

so that dns error confirms the domain isn't resolving globally, which is why railway can't verify it and why your service can't reach it

can you check your namecheap dns settings and confirm:

1. you added the exact cname record railway gave you

2. what record type you used (cname, a record, alias, etc)

3. whether you set it up for @ (root) or www

some dns providers have issues with certain configurations. once we see your actual setup i can give you more specific guidance. lots of railway users end up using cloudflare dns because it handles everything smoothly, but let's first see what you have configured

can i screenshot what i have to you? It's not sensitive and therefore safe to share in this public chat, right?

yes, please

This is from my namecheap advanced dns for leoums.dev

first thing , click "show instructions" next to "waiting for dns update" on leoums.dev in railway. that will show you exactly what cname value railway expects. compare it with your namecheap settings (10s7auml.up.railway.app) and make sure they match perfectly

if they already match and it's still stuck on "waiting for dns update" after 3 days, that's usually a namecheap issue with root domain cnames. switching to cloudflare dns (free) fixes this ; it's what a lot of railway users do when namecheap doesn't play nice. just point your namecheap nameservers to cloudflare and set up the cnames there

let me in touch

okay things work fine now. Looks like cloudflare plays much more nicely with railway than namecheap does. Thank you for your help sir.

i'm happy it works for you