You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get this error because i have only deployed instances of gpt-4o and 4o-mini.
Fail to access model(azure-gpt-35-turbo) using this api key.ERROR: Error code: 404 - {'error': {'code': 'DeploymentNotFound', 'message': 'The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.'}}
Expected behavior
The user should be able to use other models instead of GPT 3.5.
Steps to reproduce
Just try to insert you api key and deployment name under settings.
Additional information
No response
The text was updated successfully, but these errors were encountered:
What's the version of the docker image? It is fixed in latest version.
You need to mannually delete all records in DB of table llm and restart the system.
…nd openai (#2799)
### What problem does this PR solve?
#2701#2712#2749
### Type of change
-[x] Bug Fix (non-breaking change which fixes an issue)
- [x] New Feature (non-breaking change which adds functionality)
---------
Co-authored-by: Kevin Hu <[email protected]>
Halfknow
pushed a commit
to Halfknow/ragflow
that referenced
this issue
Nov 11, 2024
Is there an existing issue for the same bug?
Branch name
main
Commit ID
2e33ed3
Other environment information
No response
Actual behavior
Get this error because i have only deployed instances of gpt-4o and 4o-mini.
Fail to access model(azure-gpt-35-turbo) using this api key.ERROR: Error code: 404 - {'error': {'code': 'DeploymentNotFound', 'message': 'The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.'}}
Expected behavior
The user should be able to use other models instead of GPT 3.5.
Steps to reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: