Resolve Clerk Login Loop Issue

I’m building a web app on Replit and deploying it on Railway. Clerk’s components already render on the site and the user can submit their credentials, but after the redirect the page never reaches the dashboard—it just sits on the loading screen and repeats the sign-in loop. There’s no visible error message in the browser; the session simply never finalises.

What I need
• Review my current Clerk configuration (frontend and backend keys, JWT settings, callback URLs, environment variables).
• Check the Replit dev environment versus the Railway production build for any mismatched origins or missing secrets.
• Correct any routing or middleware that might be blocking the session token from persisting.
• Confirm that, once fixed, a successful login lands on /dashboard with the user object available on the client and server side.

Tech context
Frontend is vanilla HTML/JS with a small Express server. I can add you to the Replit project for live collaboration and give Railway console access so you can inspect logs.

Acceptance
I’ll consider the job done when I can sign in with a test account (or Google OAuth if you prefer to use that flow) and consistently reach the dashboard without being redirected back to /sign-in.

Please let me know your availability and any similar Clerk fixes you’ve handled so we can get this sorted quickly.