-
-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
You Provider Response 401: Unauthorized #1832
Comments
Same thing |
It was fixed but not pushed to pypi yet unfortunately, you will have to install |
i update to newlest, proxy is ok. |
It's working fine for me, what pc are you on, does the driver window pop up and then dissapear ?, make sure you have the latest github version, not pypi installed @bsbrother |
I just tried the new version. I must say it works, but it really overwhelmed my RAM (using ThreadPoolExecutor with 500 parallel tasks resulted in waaay too many Chrome instances). Is there another way to obtain the telemetry ID? Otherwise, it's no longer usable for my task (synthetic data generation). |
thank you @xtekky Install from source by :$ git clone https://github.com/xtekky/gpt4free the driver window pop up and then dissapear, ouput error:Provider: You telemetry generated: f152ec89-8d71-4b54-92fb-3c4a65e57950 Thank you again! |
Modify this to correct 'window.GetTelemetryID is not a function':$ diff --git a/g4f/Provider/you/har_file.py b/g4f/Provider/you/har_file.py output error:Provider: You why not login success? |
|
Modify this to correct 'window.GetTelemetryID is not a function':
$ diff --git a/g4f/Provider/you/har_file.py b/g4f/Provider/you/har_file.py
while not CAN_EVAL:
await tab.sleep(1)
-
+ await tab.sleep(2)
output error:
Provider: You
Using You provider and gpt-4 model
getting telemetry_id for you.com with nodriver
telemetry generated: 69e39500-af8b-41d6-a241-2cf068d1e2b2
You: ResponseStatusError: Response 401: Unauthorized
why not login success?
|
Thank you very much!
At 2024-04-15 17:29:42, "Tekky" ***@***.***> wrote:
image.png (view on web)
It's working fine for me, what pc are you on, does the driver window pop up and then dissapear ?, make sure you have the latest github version, not pypi installed @bsbrother
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
same problem |
The previously reported issue with the function window.GetTelemetryID not being recognized has been resolved. Additionally, the tool now supports the use of .har files as an alternative to nodriver. |
In version G4F 0.3.0.6 everything works through nodriver. But the provider has updated the list of models, could you please update it? |
thank you reply!
when upgrade, it work.
BTW, Additionally, the tool now supports the the use of .har files as an alternative to nodriver...
how to get .har files and how to active it?
thank you very much!
At 2024-04-24 05:18:52, "Hydra566" ***@***.***> wrote:
The previously reported issue with the function window.GetTelemetryID not being recognized has been resolved. Additionally, the tool now supports the use of .har files as an alternative to nodriver.
In version G4F 0.3.0.6 everything works through nodriver. But the provider has updated the list of models, could you please update it?
2024-04-24.02.10.55.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@bsbrother Here are the instructions on how to get the .har file. Everything is exactly the same, you just need to go to you.com. Then place the .har file: ./har_and_cookies/you.com.har. In general, everything you need is in the instructions posted in this section: https://github.com/xtekky/gpt4free?tab=readme-ov-file#configuration |
Hey, I haven't written instructions for you.com yet, but you should track the telemetry. It's used when you create a account. Also, you need to create an account when you track the .har file. |
Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again. |
Closing due to inactivity. |
Bug description
The provider "you" has stopped working. Everything worked fine in version 0.2.9.2. Of course I use a proxy.
Screenshots
Environment
Additional context
2024-04-13 11:51:23 ERROR:root:Response 401: Unauthorized
2024-04-13 11:51:23 Traceback (most recent call last):
2024-04-13 11:51:23 File "/app/g4f/gui/server/api.py", line 134, in _create_response_stream
2024-04-13 11:51:23 for chunk in ChatCompletion.create(**kwargs):
2024-04-13 11:51:23 File "/app/g4f/providers/base_provider.py", line 211, in create_completion
2024-04-13 11:51:23 yield loop.run_until_complete(await_callback(gen.anext))
2024-04-13 11:51:23 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-04-13 11:51:23 File "/usr/lib/python3.11/asyncio/base_events.py", line 654, in run_until_complete
2024-04-13 11:51:23 return future.result()
2024-04-13 11:51:23 ^^^^^^^^^^^^^^^
2024-04-13 11:51:23 File "/app/g4f/providers/base_provider.py", line 40, in await_callback
2024-04-13 11:51:23 return await callback()
2024-04-13 11:51:23 ^^^^^^^^^^^^^^^^
2024-04-13 11:51:23 File "/app/g4f/Provider/You.py", line 67, in create_async_generator
2024-04-13 11:51:23 cookies = await cls.get_cookies(session) if chat_mode != "default" else None
2024-04-13 11:51:23 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-04-13 11:51:23 File "/app/g4f/Provider/You.py", line 135, in get_cookies
2024-04-13 11:51:23 cls._cookies = await cls.create_cookies(client)
2024-04-13 11:51:23 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-04-13 11:51:23 File "/app/g4f/Provider/You.py", line 179, in create_cookies
2024-04-13 11:51:23 await raise_for_status(response)
2024-04-13 11:51:23 File "/app/g4f/requests/raise_for_status.py", line 28, in raise_for_status_async
2024-04-13 11:51:23 raise ResponseStatusError(f"Response {response.status}: {message}")
2024-04-13 11:51:23 g4f.errors.ResponseStatusError: Response 401: Unauthorized
2024-04-13 11:51:23 172.17.0.1 - - [13/Apr/2024 08:51:23] "POST /backend-api/v2/conversation HTTP/1.1" 200 -
2024-04-13 11:51:23 INFO:werkzeug:172.17.0.1 - - [13/Apr/2024 08:51:23] "POST /backend-api/v2/conversation HTTP/1.1" 200 -
The text was updated successfully, but these errors were encountered: