ChatGPT Desktop Login Error

ChatGPT Bugs
1

For some reason the GPT desktop app does not finish a login. I tell it to login which opens a browser tab like normal but rather than completing it with the GPT logo like normal, I get this error: This action with HTTP GET is not supported by NextAuth.js

This is not anything I did clearly because it was working fine before I wanted to switch accounts.

2

To fix this error, you need to clear the browsing data for the site that opens for login (the same one where the bug ‘Error: This action with HTTP GET is not supported by NextAuth.js’ appears).
Clear the cookies and refresh the page.

3

Alternative workaround confirmed — no cookie deletion required

I encountered the following authentication error when signing in to ChatGPT Classic on another Windows computer:

Error: This action with HTTP GET is not supported by NextAuth.js

Observed behavior:

  • ChatGPT Classic redirected the login process to the default web browser.

  • The error appeared after entering the temporary verification code.

  • An existing ChatGPT Web session was active during the initial attempts.

Workaround that resolved the issue:

  1. Signed out of all active ChatGPT sessions.

  2. Kept ChatGPT Web signed out.

  3. Started the login process from ChatGPT Classic.

  4. Completed authentication successfully using the browser.

  5. Signed in to ChatGPT Web afterward.

Both ChatGPT Classic and ChatGPT Web then worked normally.

Important: No browser cookies, browsing data or application files were deleted. No reinstallation was necessary.

This suggests a possible interaction between active web sessions and the ChatGPT Classic authentication callback. The underlying cause has not been independently verified.

I hope this alternative workaround helps other users experiencing the same issue.

4

Hi @all,

Thanks for sharing these troubleshooting steps with the community!

For anyone encountering the same error, you can try signing out of active ChatGPT sessions, clearing the site's cookies, or using a different default browser.

Is anyone still experiencing this error after trying these steps?

-Yash

5

I still have this problem.

6

I still have this problem. (2)

7

Exciting update! We just applied a fix and you all should be able to log in now without needing to clear the cache/cookies. Please let us know if you run into any further issues.