Cloudflare Vite Plugin is on one port but application thinks it's another in local dev?
It was difficult to fit the information all in in that title...
I have a React Router V7 application which I've set up with React Router's own Cloudflare template. It all works and I can deploy it. I've tried to then integrate Clerk authentication in, but because in dev mode it seems like there's some layers of proxying going on, the app itself thinks traffic is coming to it from a different port to what Vite is telling me (and expecting for resources to work properly) in the browser.
Clerk picks up on this other port (i.e. not
:5173) and sets the redirect_uri to come back to my app on this other, random port (it does change each time). When I access a page in my app it checks the auth, so this happens every time before I can even load into my app at all.
Is there a way to avoid these multiple layers of proxying while using Vite in dev mode (i.e. with HMR, etc. still working?). Am I just using this wrong and should I be using a different command altogether?)0 Replies