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

[BUG]: Wrong Gemini model names and 500 Internal Server Error #2898

Open
DangerousBerries opened this issue Dec 25, 2024 · 0 comments
Open
Labels
possible bug Bug was reported but is not confirmed or is unable to be replicated.

Comments

@DangerousBerries
Copy link

DangerousBerries commented Dec 25, 2024

How are you running AnythingLLM?

Docker (local)

What happened?

When selecting the first "Gemini Experimental 1206" from the Chat Model Selection list (there are six overall on the list), It's apparently using gemini-1.5-pro-exp-0801, not 1206, since I'm getting this error:

Could not respond to message.
[GoogleGenerativeAI Error]: Error fetching from https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-pro-exp-0801:streamGenerateContent?alt=sse: [500 Internal Server Error] An internal error has occurred. Please retry or report in https://developers.generativeai.google/guide/troubleshooting

When I select the correct "Gemini Experimental 1206" (the forth one top to bottom on the list) and try to send a prompt message, I get the same error just with the correct model.

Could not respond to message.
[GoogleGenerativeAI Error]: Error fetching from https://generativelanguage.googleapis.com/v1beta/models/gemini-exp-1206:streamGenerateContent?alt=sse: [500 Internal Server Error] An internal error has occurred. Please retry or report in https://developers.generativeai.google/guide/troubleshooting

Sucks that I've apparently been using 0801all this time before this error started, at least now I know.

@DangerousBerries DangerousBerries added the possible bug Bug was reported but is not confirmed or is unable to be replicated. label Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Bug was reported but is not confirmed or is unable to be replicated.
Projects
None yet
Development

No branches or pull requests

1 participant