getSession always returns null.

[SFin12]

I followed the tutorial up until the section where a user create a post. Within the following code copied directly from the tutorial, I keep getting getting the same error. When I log "session" after it returns it is always null even though I am logged in and the user info is all stored in the database. The only change I have made was allowing google-sign in rather than just the github sign-in.

// pages/api/post/index.ts

import { getSession } from 'next-auth/react';
import prisma from '../../../lib/prisma';

// POST /api/post
// Required fields in body: title
// Optional fields in body: content
export default async function handle(req, res) {
  const { title, content } = req.body;

  const session = await getSession({ req });
console.log(session) // always null even when signed in
  const result = await prisma.post.create({
    data: {
      title: title,
      content: content,
      author: { connect: { email: session?.user?.email } },
    },
  });
  res.json(result);
}

Here is the error:

[next-auth][error][CLIENT_FETCH_ERROR]
https://next-auth.js.org/errors#client_fetch_error undefined {
error: {},
url: 'http://localhost:3000/api/auth/session',
message: undefined
}
session null

Because of this I can't get anything to post to the database.

After searching for 3+ hours and trying many alternatives I haven't been able to resolve this.

[jharrell]

Hi @SFin12, sorry about the trouble. What tutorial, specifically? I will run through it and see if anything jumps out at me.

[SFin12]

Thanks @jharrell , here is the link to the tutorial: https://vercel.com/guides/nextjs-prisma-postgres

[jharrell]

There are a few things we can fix up/edit in that guide and I'm also running into issues!

Just to confirm @SFin12, you're running into trouble around Step 7 and 8, is that right?

I'll have to dig deeper into this and most likely publish some updates for the guide. Thank you for pointing this out!

[viktor992]

I ran into the same issue and I managed to make it work by using the getServerSession method in the api route implementation. Here's more information about my implementation: #19400 . If you agree, we could modify the guide to include these changes.

[SFin12]

@jharrell I'm mainly stuck on 8 for this problem. I'm able to sign in ( I added google sign-in along with Github) and I can see the session details on the front-end when I log it by using useSession but I'm having issues using getSession on the backend within the pages/api/post route. It throws a prisma error as well but that's only because my session is always null even if I'm signed in.

[SFin12]

To move forward with the tutorial for now, I sent the session data with the post so Prisma can use it. Probably not a secure way to do but it's a work around for now. What's interesting is that getSession seems to work within getServerSideProps for step 9 but always returns null when used in step 8.

[viktor992]

Hey @SFin12 , maybe this could be useful to you as well: #19400

[SFin12]

Awesome! I should have a chance to refactor tonight to make sure it works on my side.

[ludralph]

Hi @SFin12

do you have any more questions around this issue? If no, it would be really helpful if you could quickly mark this Discussion as answered to indicate that your issue has been resolved.

In case you do have any outstanding questions, feel free to let us know and we'd be happy to help!