a month ago
Hello,
we have got a Gateway setup, that handles multiple Domains for a Client of ours. Yesterday at around 22:00 our gateway suddenly stopped receiving traffic for the domain "www.xcarstens.de".
There were no changes made to the DNS or other systems.
In an effort to debug/solve the problem we removed the domain from the deployment an added it again. Now we were told to set an additional TXT Record to verify the domain ownership.
We did this over an hour ago, and now it is stuck in the "validating domain ownership" state.
This is a bit unfortunate, since it is a live page for a client of ours, and there ist nothing that we are aware of, that we might have done, to cause the issue.
Any help, on how to get the traffic through to our gateway would be appreciated.
Cheers
Lasse
2 Replies
25 days ago
Domain verification requires both a CNAME record and a TXT record to complete - if only the TXT record has been added, the verification will remain in the pending state. We can look into why traffic stopped at 22:00 once the domain is re-verified, but we don't have visibility into the root cause from our current investigation. It does seem that the instance is online?
Status changed to Awaiting User Response Railway • 25 days ago
angelo-railway
Domain verification requires both a CNAME record and a TXT record to complete - if only the TXT record has been added, the verification will remain in the pending state. We can look into why traffic stopped at 22:00 once the domain is re-verified, but we don't have visibility into the root cause from our current investigation. It does seem that the instance is online?
25 days ago
Hey,
thanks a lot for the reply - We managed to get it working again at around 13:00 yesterday, so the service was offline for about 15 hours.
The CNAME was already set, after the problem occured we initially just added the TXT record.
At around 12:00 we tried switching our deployment to vercel, so we changed the CNAME record to be pointing to vercel.
Since that didnt work just out of the box, we tried switching back to Railway at around 13:00 - Then it worked.
It would still be good to know, what caused the problem initially - As I said, we didnt change anything regarding the DNS Setup or the custom domains in Railway, so it ist still unknown why we stopped getting traffic.
Any debugging / updates would be appreciated.
Cheers
Lasse
Status changed to Awaiting Railway Response Railway • 25 days ago