a month ago
▎ Hi Railway team,
▎
▎ My service works fine on its *.up.railway.app URL, but my custom domain www.balkonova.de does not load in
▎ the browser, even though the dashboard shows it as Active.
▎
▎ HTTPS requests to the domain fail with a TLS certificate mismatch — your edge serves a *.up.railway.app
▎ certificate instead of one for www.balkonova.de.
▎
▎ DNS points to gelpqtqk.up.railway.app and the service itself is healthy.
▎
▎ Could you please investigate what's going wrong on your side and tell me the cause? I'd rather understand
▎ where it fails than guess at a fix.
THanks
Pinned Solution
a month ago
You need to add a TXT record to _railway-verify.www.balkonova.de. If you’re using the API, you can find the content for the record from the verificationToken property under status.
3 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
You need to add a TXT record to _railway-verify.www.balkonova.de. If you’re using the API, you can find the content for the record from the verificationToken property under status.
a month ago
Thanks mate for trying to help me. But fuck railway didn't expect it to be such a f pain. already having problems on the easiest step. not my first time doing his.
a month ago
There isn`t even any kind of support or something
Status changed to Solved 0x5b62656e5d • about 1 month ago