next-auth not working with serverless-nextjs

Describe the bug

I deployed my app to Cloudfront, S3, and AWS Lambda Edge using serverless-nextjs component offered by serverless.com.

I am getting a 503 error with next-auth when I try to redirect to /api/auth/signin. I also get the same error if I try to load the signin page directly without a redirect.

The Lambda function associated with the CloudFront distribution is invalid or doesn’t have the required permissions. We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Code:

export async function getServerSideProps(context) {
  const session = await getSession(context);

  if (!session) {
    return {
      redirect: {
        destination: '/api/auth/signin',
        permanent: false,
      },
    }
  }
...
}

Serverless.yml:

myNextApp:
  org: myOrg
  stage: prod
  component: "@sls-next/serverless-component@1.18.0" # it is recommended you pin the latest stable version of serverless-next.js
  inputs:
    bucketName: myApp-nextjs
    region: us-east-1
    name: myApp

Actual behavior

Next-auth api endpoints are not working.

Expected behavior

I expected the app to work the same way it does locally. I redirect to a signin page generated by next-auth when the user is not logged in.

[jeremygottfried]

I believe I am using the built-in one:

import Adapters from 'next-auth/adapters'

...
adapter: Adapters.Prisma.Adapter({ prisma })

ERROR [next-auth][error][get_user_by_provider_account_id_error] https://next-auth.js.org/errors#get_user_by_provider_account_id_error PrismaClientInitializationError2 [PrismaClientInitializationError]: Query engine binary for current platform “rhel-openssl-1.0.x” could not be found. This probably happens, because you built Prisma Client on a different platform. (Prisma Client looked in “/tmp/query-engine-rhel-openssl-1.0.x”)

Searched Locations:

You already added the platforms “native”, “rhel-openssl-1.0.x” to the “generator” block in the “schema.prisma” file as described in https://pris.ly/d/client-generator, but something went wrong. That’s suboptimal.

Please create an issue at https://github.com/prisma/prisma-client-js/issues/new at PrismaClientFetcher.request (/var/task/pages/api/auth/[…nextauth].js:151931:15) at processTicksAndRejections (internal/process/task_queues.js:97:5) { clientVersion: ‘2.16.1’ }

I have tried many different solutions, talked about here:

• serverless-next.js#843
• prisma/docs#841
• next-auth#1191
• prisma/prisma#2195
• prisma-client-js#616
• prisma/prisma#5392

I’m going to reopen this issue in prisma and serverless-next.js because it seems to be more of an issue on their end, but if you have any ideas how to solve I would be very greatful!

[tranthaison1231]

@ThangHuuVu Can you help me check this