24 days ago
Hi Railway team,
My custom domain b2b.matpoz.pl has been stuck on "Validating domain ownership" for over 24 hours, and no SSL certificate is being issued.
Project ID: 95ee733d-a153-4682-adfc-11595d61fbdc
Service: matpoz-b2b (public URL: matpoz-b2b.up.railway.app – works correctly)
Custom domain: b2b.matpoz.pl (target port 8080)
DNS provider: OVH
The required DNS records are configured exactly as Railway specified and are fully propagated worldwide (verified on whatsmydns.net across most global locations):
CNAME: b2b.matpoz.pl → sofyk99l.up.railway.app
TXT: _railway-verify.b2b.matpoz.pl → railway-verify=e71296531faf8182a5808ee1e37db2e3da675c9dd1c08bf68df83e75c08e48a6
The railway-verify TXT resolves to the exact value above on the authoritative nameservers and on the large majority of public resolvers globally. There are no conflicting A/AAAA records. Only the custom-domain validation and certificate issuance are stuck – the public *.up.railway.app URL works fine.
Since the records are correct and live, the validation appears to be stuck on your side. Could you please trigger a fresh validation / certificate issuance cycle for this domain?
If the expected values have changed, please note that the dashboard only displays the required CNAME and TXT once when the domain is added, with no way to view them again afterwards. If the current expectation differs from the records above, please confirm the exact CNAME target and railway-verify TXT token you now expect, and I will update DNS accordingly.
Thank you for your help,
Marcin Lisiak
COO, MAT-POŻ
b2b.matpoz.pl
2 Replies
24 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 24 days ago
24 days ago
I suggest that you remove your custom domain, and all its related DNS records, wait for 10 ~ 15 mins, and add it again.
24 days ago
Since the DNS records appear correct and propagated, please try removing the custom domain from Railway, waiting around 10–20 minutes, then adding it again with target port 8080. After re-adding, copy the newly shown CNAME and TXT records from Railway and update OVH only if the values changed. Then wait up to an hour for validation and SSL issuance. Avoid repeating this multiple times because of Let’s Encrypt rate limits.