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
raise private key not found when set llm key #4258
Comments
the dify 0.6.6 also report that error |
Hey @cjdxhjj, great to see you back! 🙌 I'm diving into the details of your issue and will get back to you shortly with some insights. |
The error indicating "Private key not found" suggests an issue with locating the private key for the specified tenant ID. This problem often arises from the encryption keys not being properly set up or accessible in your environment. To address this, you should reset the encryption keys. Here's how you can do it for both Docker and source code setups:
This process is detailed in the Dify documentation's FAQ section, which provides guidance on handling encryption key-related issues. Additionally, ensure that your Redis cache is functioning correctly, as Dify uses Redis to cache private keys for efficiency. Issues with Redis, such as connectivity problems or incorrect cache eviction policies, could lead to the application being unable to retrieve the private key from the cache, thus attempting to load it from storage and resulting in the error you're experiencing. If resetting the encryption keys does not resolve the issue, it may be necessary to review the application's configuration regarding key storage and retrieval, as well as ensuring that the Redis cache is properly configured and accessible.
|
Self Checks
Dify version
0.6.7
Cloud or Self Hosted
Self Hosted (Docker), Self Hosted (Source)
Steps to reproduce
when i set the llm secret it report an error
✔️ Expected Behavior
No response
❌ Actual Behavior
the docker report error
self host
The text was updated successfully, but these errors were encountered: