What domain are you trying to add?

A domain that I purchase at hostinger.

Can you share the domain you're trying to add?

awaken.at

Make sure the port your application is listening to is the same port your URL is mapped to and it's listening to 0.0.0.0 instead of localhost or something else.

Almost there... the current issue now is the "not secure". How to apply SSL?

You need to add a TXT record to _railway-verify.awaken.at.

Now if I type www.awaken.at, works, but if I type awaken.at, not found.

Try removing awaken.at from Railway and add it back after ~10-15 mins. Update DNS records as necessary.

Doubt, for custom domains, should I put both, www.awaken.at and awaken.at?

If you wish to use both www.awaken.at and awaken.at, then yes, you'd need to add both domains to the service.

Also, make sure to disable the parking page in your Hostinger dashboard if you haven't yet.

Hey there,

it looks like you hit a few of the classic snags when linking a Hostinger domain to Railway. Here is a complete checklist to get your React app running smoothly on both the root and www domains with proper SSL:

1. Fix the "Train has not arrived" error

This means Railway is successfully running your app, but its internal router can't connect to it. Your React app needs to listen on 0.0.0.0 (all interfaces) instead of localhost, and it must use Railway's dynamic port.

• If you are using Vite, just update your package.json start/preview script to include the host flag: "start": "vite --host".
• Ensure you aren't hardcoding a port like 3000 in your server files; always use process.env.PORT.

2. Add both domains in Railway

Railway treats your root domain (awaken.at) and the subdomain (www.awaken.at) as entirely separate entities. You need to go to Settings > Networking > Custom Domains in your Railway project and click "Add Custom Domain" twice — once for the root, and once for the www version.

3. Configure Hostinger DNS & Fix SSL

Those dns-parking.com nameservers mean Hostinger currently has your domain parked. Head into Hostinger's DNS Zone Editor and add these records:

• For the www domain: Add a CNAME record with the host set to www and point it to the Railway domain they gave you (e.g., your-app.up.railway.app).
• For the root domain: Add an A record (or ALIAS) with the host set to @ pointing to the IP address Railway provides in your settings.
• To fix the "Not Secure" SSL warning: Railway needs to verify you actually own the domain before it generates the certificate. Add a TXT record with the name _railway-verify and paste the verification string Railway shows in your dashboard.

Pro tip: DNS propagation can be annoying. If Railway gets stuck trying to verify your SSL after you update Hostinger, just delete the custom domains from your Railway dashboard, wait about 10-15 minutes, and add them back. This forces Railway to clear its cache and pull your fresh DNS records.

Hope this helps you get it sorted!