Also, there is no api like /api/auth. You may want to query /api/auth/signin or something else that exists.. You can see the list of APIs here: https://github.com/supertokens/frontend-driver-interface/blob/master/v1.8.0.md

I am using the one provided here:

what does your backend and frontend config look like?

i mean the appInfo object

its the one provided in this step of the guide.

Have you set

apiBasePath: "/api/auth/"

in the appInfo?

js
let appInfo = {
  // learn more about this on https://supertokens.io/docs/thirdparty/appinfo
  appName: 'SuperTokens Demo App', // TODO: Your app name
  websiteDomain: "http://localhost:3000", // TODO: Add your website domain
  apiDomain: "http://localhost:3000", // TODO: should be equal to `websiteDomain` in case using the `api` folder for APIs
  apiBasePath: "/api/auth/", // /api/auth/* will be where APIs like sign out, sign in will be exposed 
}

This is my current appInfo (i havent changed anything from the guide)

this is really strange...

can you print a console log in the auth serverless function to see if that get's called?

I have a feeling that this is a Vercel problem. I have already asked their support team about it since I also ran into an issue like this while using Auth0

I see..

does this help you: https://github.com/supertokens/supertokens-node/issues/118

I will try it and update you

👍

Sadly that didnt fix it too. I have set it up like this: Vercel recognises the serverless function (have tried that by specifying a runtime) but sadly i still get the 404 errors

i'll have a look in sometime @User

I have also added the console.log but that didnt output anything. I will post something about it here if Vercel has an update on it and thank you!

@User do you think this might be the issue that's causing 404? https://github.com/vercel/vercel/discussions/5256#discussioncomment-91290

that looks really good thank you for looking into it I really appreciate it! I will look into it and check if there is a way to rename the root api folder and still use those serverless functions.

I have tried to remove the pages api folder (which isnt the intended way) which worked with self made js files (even if they are in the auth folder) but the localhost:3000/auth page still gets 404s on the refresh api calls

Hmmmm

Are any of your other APIs reachable?

Also, https://stackoverflow.com/a/65817501

yes everything else is reachable and if i remove my other API folder everything supertoken related works. I guess the problem is the one you linked above but I would prefer not having to remove my other serverless functions since they handle the backend logic in this project. I just am confused why other js serverless functions work when i move them into the root level api folder but the catch all route which supertokens uses doesnt.

I think it might be related to the dynamic routing that’s needed in our case. /api/auth/* as opposed to other APIs which all have a specific path

Yeah that could be the case

How would one go about with doing this in the backend?

On the backend, you should have some env var set by whatever serverless env you have deployed on which will allow you to read the domain

so print out the value of

process.env

and you should see some var that has the domain