Closed kienmd closed 1 year ago
Yeah looks like it's due to the new Cloudflare protection that OpenAI added. Will track the issue in this thread and then update the extension when there's a fix.
I am writing the token manually in the .env SESSION_TOKEN= as soon as I log into chatgpt I go to the cookies and copy the secure auth token but stills shows the error even if I do the capcha manually any solutions or everyone is having the same problem even with manual? Because I did the transitive bs examples and they worked even if I had to do the capcha manually
$ node server.js
node --trace-warnings ...
to show where the warning was created)
× Connecting to ChatGPT
file:///E:/DB/ChatGPT/chatgpt-chrome-extension/node_modules/chatgpt/build/index.js:264
throw new Error(ChatGPT failed to refresh auth token. ${err.toString()}
);
^Error: ChatGPT failed to refresh auth token. Error: 403 Forbidden at ChatGPTAPI.refreshAccessToken (file:///E:/DB/ChatGPT/chatgpt-chrome-extension/node_modules/chatgpt/build/index.js :264:13) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async ChatGPTAPI.ensureAuth (file:///E:/DB/ChatGPT/chatgpt-chrome-extension/node_modules/chatgpt/build/index.js:2 30:12) at async oraPromise (file:///E:/DB/ChatGPT/chatgpt-chrome-extension/node_modules/ora/index.js:368:18) at async start (file:///E:/DB/ChatGPT/chatgpt-chrome-extension/server.js:36:3)
Node.js v18.12.1
Yep - same problem here. Ugh.
Same problem here:
Getting this error after adding the session token to .env file.
Error: ChatGPT failed to refresh auth token. Error: 403 Forbidden
This works for me thanks. However, I found another cool extension, called Merlin.
@gragland
Yeah looks like it's due to the new Cloudflare protection that OpenAI added. Will track the issue in this thread and then update the extension when there's a fix.
@gragland Are you planning to update the code and readme based on changes made in the transitive-bs thread? I am still getting the same error message.
Thanks @sellenth! Just merged your pull request and updated to the latest version of the library.
Being thrown this error, not sure if it is to do with new Cloudflare protections.