My custom domain www.meutarotapp.com returns a 301 redirect loop to itself from server: railway-edge. The request never reaches my container. My other custom domain www.meutarot.com on the same service works correctly. I've tried: removing/re-adding the domain, changing port configuration, and redeploying. SSL cert is valid (Let's Encrypt).

Evidence:

curl -sI -H "Host: www.meutarotapp.com" https://web-production-857f.up.railway.app/
→ HTTP/2 301, location: https://www.meutarotapp.com/

curl -sI -H "Host: www.meutarot.com" https://web-production-857f.up.railway.app/
→ HTTP/2 302, location: /en

Additional context:

• This domain was previously pointed at Squarespace. I've since fully removed it from Squarespace (over 24 hours ago).
• I've deleted and re-added the domain in Railway twice. The second time, Railway assigned a new CNAME target (nno6uq3h.up.railway.app replacing the original cmrqby5s.up.railway.app). Both DNS records show green in Railway settings, and the SSL cert (Let's Encrypt) was re-issued successfully.
• I've also triggered a manual redeployment — the 301 self-redirect persists.
• The domain www.meutarot.com on the exact same service works perfectly, confirming the app container is healthy.

It seems like Railway's edge proxy has a stale/broken routing rule specifically for www.meutarotapp.com that survived domain removal and re-addition.