I've got a super weird problem trying to implement Supertokens in a NextJS app for the first time. Using a NestJS backend and everything appears to be configured properly but when I try to sign up with Nest it hits my NestJS backend and then returns a 404. If I hit the exact same URL from the failed network request using CURL it works just fine eg:

http://localhost:3000/api/auth/signup/email/exists?email={email}

returns the expected result. If I visit the email exists URL directly in the browser it also prints the expected JSON. For some reason though the fetch that's getting triggered from the Next app always returns 404 🤔 Its not a CORS error... just a 404 as if the endpoint doesn't exist. I can log and see it hitting the supertokens middleware in all cases

Hi @wonderpandadev Glad you got it working! Just a quick pointer, if you enable debug logs in the backend it usually provides more information about why the SDK responded in a specific way. For example in your case it would have printed information about not finding any recipe matching the

rid

Thank you!