2 months ago
Getting:
This server could not prove that it is [domain]; its security certificate expired 5 days ago. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to Thursday, March 26, 2026. Does that look right? If not, you should correct your system's clock and then refresh this page.
project Id: a83758cd-7f2e-490a-814b-83a31c1dc56d
1 Replies
Seems issue could've been because it was missing a "_railway-verify[.subdomain]" TXT record? Was never prompted to add that record, whenever Railway started requiring it. Wasn't needed when I initially started using Railway, and set up this service.
Would be good to auto-prompt the user to either re-add their custom domain, or say there's a new DNS record needed so it's obvious I need to add that new record, even if it wasn't needed before.
Either way, the solution was remove custom domain and re-add it, then re-configure DNS settings.
Status changed to Solved brody • about 2 months ago