Go to NameSilo - Manage DNS for your domain.

For www, you should have ONLY ONE record:

Type: CNAME

Host: www

Value/Target: (The Railway CNAME value, e.g., cname.railway.app)

NO other A, CNAME, or URL Redirect records for www.

For the root domain (@), follow Railway's instructions (usually an A or CNAME record, as given by them).

Double-check:

NO “Forward” or “Redirect” set for www in NameSilo.

DNSSEC: Make sure it's OFF.

TTL: You can set to lowest (like 1 min) for quick propagation, but not critical.

If STILL Stuck after 1–2 Hours

Double-check again at dnschecker.org for www CNAME — it must match Railway’s value everywhere.

Hey! When it gets stuck at "Issuing TLS certificate" like that, it usually means something's not quite right with your DNS setup — most likely with the CNAME record.

A few things to double-check:

1. CNAME is set for www, not the root (@). Railway only issues certificates for subdomains like www.example.com, not the bare domain.
2. Make sure your CNAME for www is pointing exactly to the value Railway gives you (something like xxxx.up.railway.app.).
3. After saving the CNAME, it can take a few minutes (sometimes up to an hour) for DNS to propagate — so be patient and try refreshing later.
4. Try running a DNS check at https://dnschecker.org for www.yourdomain.com — you should see it resolving to yourapp.up.railway.app.

Also make sure you're adding www.yourdomain.com (not just yourdomain.com) to the Custom Domains section in Railway.