Im getting error 403 Fobidden

[DrMemoryFish]

Error loading webview: Error: Could not register service workers: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state.

An error occurred. If the issue persists try 'ChatGPT: Clear session.'

I get the above error codes. I've refreshed and cleared many times.

[gregid]

I started getting 403 Forbidden yesterday evening - I wondered if anyone else is having similar problem. I assumed OpenAI may have throtthled access from outside of their web ui.
I didn't have ServiceWorker error though (just 403).

[xichen-de]

I also started getting 403 Forbidden today. The problem persists even after deleting the session. Looks like OpenAI is restricting access.

[Joey0x646576]

According to the creator of chatgpt-api they added additional cloudflare protection.

To bypass this you need two additional properties; cf_clearance and user-agent. While this works, it's only available for a limited time, before you need to refresh your cf_clearance token.

This package is not updated with the latest chatgpt-api, but if you update the dependencies and build it yourself it will still function.

[gencay]

Hi - yes, there have been multiple changes on the openai side. I am working on a resolution

[gencay]

Update: ChatGPT servers are completely down right now that blocks development progress. I will update again if/when I find a resolution for our extension. Thanks all for the patience!

[gencay]

Update: Hang tight, the VSCode marketplace package seems to not include puppeteer built-in chromium. Thus there are run-time errors in the extension. WIP

Hi everybody,

I've a fix for the recent 403 issue and it's being rolled out right now. Please watch out the version 1.7.1 on marketplace 🎉

The new workflow logs you in automatically without needing to copy paste the cookies onto the extension:

• Enter your email address
• Enter your password (We don't store anything, all personal information remains locally on your vs-code)

Let the login flow automatically run:

• It'll open a new chrome instance and use the credentials you provided to automatically login and grab the required fields from your cookie.

Since OpenAI servers are experiencing issues, please expect intermittent login failures / outage messages on openai website during auto-login flow.

This is the first attempt to overcome the 403 errors. Let me know if you face issues. I will keep the Issue open until we are good with the current solution.

[raifpy]

What about OAuth?

[gencay]

Mitigation in place: Add your session cookies and userAgent manually. You can grab these from session cookies cf_clearance and __Secure-next-auth.session-token + run this in console to get your User Agent: navigator.userAgent.

I'm working on an auto-login flow which I mentioned in my earlier message. This will be much neater than refreshing those cookies manually. The v1.7.2 now works when you provide session-token, cf_clearance and userAgent variables.

[gregid]

Run the following command in Console to find your user agent: navigator.userAgent. Enter the content of this value when prompted by the extension.

I would change it to:

Run the following command in (web browser) Console to find your user agent: navigator.userAgent. Enter the content of this value when prompted by the extension (no single or double quotes).

• The first part (console) got me confused for a moment :)
• The quotes - only second time after I avoided quotes in copying and pasting it worked - not sure if just a fluke or one should exclude these quotes.

[GitHdu]

Update: Hang tight, the VSCode marketplace package seems to not include puppeteer built-in chromium. Thus there are run-time errors in the extension. WIP

Hi everybody,

I've a fix for the recent 403 issue and it's being rolled out right now. Please watch out the version 1.7.1 on marketplace 🎉

The new workflow logs you in automatically without needing to copy paste the cookies onto the extension:

• Enter your email address
• Enter your password (We don't store anything, all personal information remains locally on your vs-code)

Let the login flow automatically run:

• It'll open a new chrome instance and use the credentials you provided to automatically login and grab the required fields from your cookie.

Since OpenAI servers are experiencing issues, please expect intermittent login failures / outage messages on openai website during auto-login flow.

This is the first attempt to overcome the 403 errors. Let me know if you face issues. I will keep the Issue open until we are good with the current solution.

still getting 403 forbidden

[curtisreynolds57]

Update: Hang tight, the VSCode marketplace package seems to not include puppeteer built-in chromium. Thus there are run-time errors in the extension. WIP
Hi everybody,
I've a fix for the recent 403 issue and it's being rolled out right now. Please watch out the version 1.7.1 on marketplace 🎉
The new workflow logs you in automatically without needing to copy paste the cookies onto the extension:

• Enter your email address
• Enter your password (We don't store anything, all personal information remains locally on your vs-code)

Let the login flow automatically run:

• It'll open a new chrome instance and use the credentials you provided to automatically login and grab the required fields from your cookie.

Since OpenAI servers are experiencing issues, please expect intermittent login failures / outage messages on openai website during auto-login flow.
This is the first attempt to overcome the 403 errors. Let me know if you face issues. I will keep the Issue open until we are good with the current solution.

still getting 403 forbidden

I believe he hasn't released the fix, yet.

[gencay]

I did release the fix and the new flow that requires session token, clearance token and user agent. Check the Readme.md for getting those.

[gencay]

The issues seem to be happening for some users of the downstream API wrapper we are using. There is an active discussion here: transitive-bullshit/agentic#96 (comment). Some people reported that getting the required tokens and user-agent using a different browser than Chrome helped them bypass the 403 issues.