Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to fetch Auth value (403, Forbidden), supply path to correct cookies #19

Open
t-mck opened this issue Jun 18, 2024 · 5 comments
Open

Comments

@t-mck
Copy link

t-mck commented Jun 18, 2024

I routinely get the following error despite following the setup instructions:

WebChatGPT.errors.VerificationError: Failed to fetch Auth value (403, Forbidden), supply path to correct cookies. Incase you have no idea on how to get the cookies check the documentation at - https://github.com/Simatwa/WebChatGPT

I have a copy of the cookies.json, I am running python 3.10, have an open instance of the model running in either Google Chrome, or Firefox (both fail for the same reason, and I recreated my cookies file when I switch browsers).

I have noticed that the url used throughout the code is some version of: https://chat.openai.com, and that OpenAI has changed that to https://chatgpt.com. So in order to troubleshoot I changed every instance of that url in the utils.py, however it does not fix the problem.

Note that my code routine gets a 403 error after running line 101 of the Utils.py file, and on line 106 there is comment that says: "# This sh*t here is raising http 403 in Python 3.9. Consider fixing it.", I'm wondering if there is an updated in an underlying library that is causing python 3.10 to end up with a 403 error? Or if it is some OpenAI change, or something I am doing incorrectly.

@11100010
Copy link

same issue too

@tddevel
Copy link

tddevel commented Jun 28, 2024

have the same problem

@dongyups
Copy link

same Failed to fetch Auth value (403, Forbidden), waiting for the solution.

@progeroffline
Copy link

same issue

@tares003
Copy link

tares003 commented Jan 1, 2025

any fix for this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants