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

Report "Not a valid PEM pre boundary" error when I add a model #4238

Open
4 tasks done
WhiteRoseinShangHai opened this issue May 10, 2024 · 4 comments
Open
4 tasks done
Labels
🐞 bug Something isn't working

Comments

@WhiteRoseinShangHai
Copy link

Self Checks

  • This is only for bug report, if you would like to ask a quesion, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

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.image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Copy link

dosubot bot commented May 10, 2024

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 -----BEGIN CERTIFICATE----- and end with -----END CERTIFICATE-----.

To address this issue, ensure that:

  • Any SSL/TLS certificates used by Dify or required for communication with external services over HTTPS are correctly formatted.
  • Check Dify's configuration for any SSL/TLS certificate settings, ensuring they are correctly implemented.
  • If a network proxy or firewall is part of your setup and uses SSL/TLS certificates, verify their configuration as well.

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.

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

@dosubot dosubot bot added the 🐞 bug Something isn't working label May 10, 2024
@WhiteRoseinShangHai
Copy link
Author

I use dify in private net,it don't have domain, so I doesn't use ssl, use http not https

@Hansen523
Copy link

@dosu I use dify in private net,it don't have domain, so I doesn't use ssl, use http not https

@zeroameli
Copy link

@WhiteRoseinShangHai Try checking the "encrypt_public_key" in table "tenants", it seem you got an invalid value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants