4 months ago
I have a running site with Cloudflare DNS provider and using Clerk to authenticate users. Today, I switched Clerk Auth from development to production, and added the Cloudflare DNS records for the Clerk Domains, including Frontend API, Account portal, and Email (three DNSs) mandated by the Clerk.
The Clerk showed them successfully verified and issued SSL certificates on its Domains Dashboard.
I also configured my Railway services with the Clerk Production's NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_SECRET_KEY, and CLERK_WEBHOOK_SECRET accordingly.
However, when I ran my site in the browser, I got a Not Found page with the message as follows:
'''
The train has not arrived at the station.
Please check your network settings to confirm that your domain has provisioned.
If you are a visitor, please let the owner know you're stuck at the station.
Request ID:
DhJqoiEzRCSQ343tLPU1MQ
'''
and the log errors in the Browser's console, looking like:
'''
GET https://mysite-domain-name/sign-in 404 (Not Found)
Navigated to https://mysite-domain-name/sign-in
GET https://mysite-domain-name/ 404 (Not Found)
Navigated to https://mysite-domain-name/
'''
Could anyone shed some light on what configuration(s) I am missing?
Thanks
3 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
A redeploy should fix this, but we will be looking into why this has happened.
Status changed to Awaiting User Response Railway • 4 months ago
brody
A redeploy should fix this, but we will be looking into why this has happened.
4 months ago
Thanks, Brody. I redeployed and online again now.
Status changed to Awaiting Railway Response Railway • 4 months ago
Status changed to Solved chris-opendata • 4 months ago
4 months ago
The underlying issue is resolved and you shouldn't see this again.
Status changed to Awaiting User Response Railway • 4 months ago
Status changed to Solved sam-a • 4 months ago