I am just starting to work with supertokens. I prepared the project as in the tutorial for AWS lambda. I stopped at the 404 problem and prepared the frontend on this init: appInfo: { appName: "SuperTokens Demo App", apiDomain: "https://api.example.com", apiBasePath: "/auth", apiGatewayPath: "/", websiteDomain: "https://frontend.example.com", }, I prebuild UI and i works. When I try type email to sign up I see network issue: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: GET Status Code: 404 Not Found But when I opened this page I see response: {"status":"OK","exists":false} CORS works: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: OPTIONS Status Code: 200 OK I use the API GW V2 with integration for route: ANY /auth/{PROXY+}

hey @chilldamiano

At the moment I'm using Managed. service

what are the recipes you have init on the frontend and on the backend in the recipeList?