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
Report "Not a valid PEM pre boundary" error when I add a model #4238
Comments
The error "Not a valid PEM pre boundary" you're encountering typically indicates an issue with the formatting of SSL/TLS certificates, particularly when a certificate does not have the correct PEM (Privacy Enhanced Mail) headers. This can happen if Dify is trying to establish a secure HTTPS connection and the certificate involved is improperly formatted. A properly formatted PEM certificate should start with To address this issue, ensure that:
This error might not be directly related to the process of adding a model in Dify but could stem from how Dify is set up to communicate over HTTPS, either internally or with external services. If you can provide more details about the specific context in which this error occurs, it would help in identifying a more precise solution.
|
I use dify in private net,it don't have domain, so I doesn't use ssl, use http not https |
@dosu I use dify in private net,it don't have domain, so I doesn't use ssl, use http not https |
@WhiteRoseinShangHai Try checking the "encrypt_public_key" in table "tenants", it seem you got an invalid value. |
Self Checks
Dify version
0.6.7
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
when I add a model, report "Not a valid PEM pre boundary" error, I try add Zhipu and deepseek model.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: