Update — 28 Apr 2026, 22:03 Madrid time

DNS is still correct and propagated:

www.feriamedievalelalamo.es CNAME 2lua1x8z.up.railway.app

_railway-verify.www.feriamedievalelalamo.es TXT railway-verify=121270d2646c7769f1338f75788d879b7359a06116741b9022e33bd8e619853e

Verified from:

dns1.barmetmedia.es

dns2.barmetmedia.es

1.1.1.1

8.8.8.8

The site responds through Railway:

HTTP/2 200

server: railway-edge

But TLS still serves the fallback certificate:

subject=CN=*.up.railway.app

issuer=Certainly Intermediate R1

SAN: DNS:*.up.railway.app

Expected certificate:

www.feriamedievalelalamo.es

I'd recommend removing the A record on your root domain.

Also, try removing your www domain from Railway, waiting for ~10-15 mins, then add it back.

Failed to issue TLS certificate

I did it as you mention. I delete the A record and create the www again with Railway new settings

You may have hit a LE certificate rate limit. Unfortunately, if this is the case, you'd need to wait until next week to get a certificate.

The team has identified the issue regarding TLS certificates and is working on it.

https://status.railway.com/incident/C4L89HAF

Fastly has resolved the issue. Try removing the custom domain from Railway and add it back.