Timeout when using getSession() Session Server-side

[mdavish]

I'm encountering an issue where every time I try to use getSession() server-side, the api/auth/session endpoint times out.

I was encountering this on my own project, and then I tried to refer to the example repo and had the exact same problem. When I try to access the server page from the example repo (the one that does server side rendering with getSession) I keep getting this error:

[next-auth][error][client_fetch_error] 
https://next-auth.js.org/errors#client_fetch_error session FetchError: request to http://localhost:3000/api/auth/session failed, reason: connect ETIMEDOUT 127.0.0.1:3000
    at ClientRequest.<anonymous> (/Users/mdavish/next-auth-example/node_modules/node-fetch/lib/index.js:1461:11)
    at ClientRequest.emit (events.js:311:20)
    at ClientRequest.EventEmitter.emit (domain.js:482:12)
    at Socket.socketErrorListener (_http_client.js:426:9)
    at Socket.emit (events.js:311:20)
    at Socket.EventEmitter.emit (domain.js:482:12)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  message: 'request to http://localhost:3000/api/auth/session failed, reason: connect ETIMEDOUT 127.0.0.1:3000',
  type: 'system',
  errno: 'ETIMEDOUT',
  code: 'ETIMEDOUT'
}

But then when I hit this endpoint directly in my browser (http://localhost:3000/api/auth/session) it returns perfectly fine and doesn't time out.

Anyone have any idea what's going on here?

[balazsorban44]

Might be related to #1535. #2857 lays the groundwork for a fix.