-
Notifications
You must be signed in to change notification settings - Fork 60.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
[BUG] Anthropic Claude 3 Error Message - json { "error": true, "message": "Failed to fetch" } #4687
Comments
Are you using desktop app of NextChat? |
Yes, Windows 10 and Ubuntu Desktop. Both Version 2.12.3. Same error on both installations. |
i have the same problem |
i have the same problem too. |
Also having issue on windows 11 desktop |
{ |
what happened Who can say |
Try to change your proxy. I've delt with it. |
Having the same issue. Any resolve soon? |
I didn't change anything. I added my api and that's it. |
I am having the same issue. Is there any resolve soon? |
I stopped using because of this with Anthropic API, last update (2.15.6 mac m1) seemed to fix then mid chat (~50 msgs, no change to settings) got the same error again. No issue with OpenAI. Haven't found a fix (new API's added, changed max tokens) and have had to stop using NextChat again.
And working again, no other change, in 2.15.7. |
我遇到了同样的问题。能尽快解决吗? |
I encountered the same problem. Can it be solved as soon as possible? |
Bug Description
Any chat requests using any of the models: Sonnet, Haiku or Opus result in the error message:
Steps to Reproduce
In settings:
Model Provider: Anthropic
Endpoint Address: https://api.anthropic.com
Anthropic API Key: Entered (verified working elsewhere)
API Version: 2023-06-01
Custom Models: left blank
Model: claude-opus-3-20240229(Anthropic)
All other settings as per default.
Expected Behavior
Normal chat response from server.
Screenshots
Deployment Method
Desktop OS
Windows 10
Desktop Browser
Firefox
Desktop Browser Version
Windows Version 2.12.3
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered: