Skip to content

Navigation Menu

Sign in
Appearance settings
Sign up
Appearance settings
Discussion options

Hello everyone, I'm new to next-auth and this is my first discussion post here. Looking forward to being apart of the community!

When cloning the next-auth-example repo on my personal windows machine, everything works perfectly.

However, on my M1 Mac, when cloning the exact same repo, I'm met with the following errors...

Screen Shot 2022-11-02 at 12 03 50 PM

The redirects seem to be bouncing between 'session' & 'session/' as shown below until it errors...

Screen Shot 2022-11-02 at 12 07 27 PM


I'm aware that CLIENT_FETCH_ERROR is normally resolved by setting a NEXTAUTH_URL .env variable, which I have. Here is my .env.local

NEXTAUTH_URL=http://localhost:3000
NEXTAUTH_SECRET=<insert-randomly-generated-hex32-value>

I've tried setting NEXTAUTH_URL=http://127.0.0.1:3000 and the same error occurs.

When attempting to Sign In, I'm redirected to http://localhost:3000/api/auth/error where only the following is displayed.

Screen Shot 2022-11-02 at 12 22 57 PM

Any thoughts would be greatly appreciated!


System:

  • OS: macOS 12.6
  • CPU: (8) arm64 Apple M1 Pro
  • Memory: 105.63 MB / 16.00 GB
  • Shell: 5.8.1 - /bin/zsh

Binaries:

  • Node: 16.18.0 - /usr/local/bin/node
  • Yarn: 1.22.19 - /opt/homebrew/bin/yarn
  • npm: 8.19.2 - /opt/homebrew/bin/npm

Browsers:

  • Chrome: 107.0.5304.87
  • Safari: 16.1

npmPackages:

  • next: 12.2.5 => 12.2.5
  • next-auth: 4.15.0 => 4.15.0
  • react: ^18.2.0 => 18.2.0
You must be logged in to vote

Super odd, however, after re-installing node w/ brew, deleting all generated project files, and giving the mac a fresh restart things seem to be working now. I guess the typical, "turn it off/on again" was the case here.

No real conclusion as to what was causing this issue, but nonetheless, it's resolved. 🤷🏽

Replies: 1 comment · 1 reply

Comment options

Super odd, however, after re-installing node w/ brew, deleting all generated project files, and giving the mac a fresh restart things seem to be working now. I guess the typical, "turn it off/on again" was the case here.

No real conclusion as to what was causing this issue, but nonetheless, it's resolved. 🤷🏽

You must be logged in to vote
1 reply
@NorkzYT
Comment options

@TorbynNare

I have the same issue, I have done all that you have said, any ideas?

Here is my issue.
#5805

Answer selected by TorbynNare
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Help
Labels
None yet
2 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.