Model provider reports Internal Server Error

[tyutltf]

Self Checks

• This is only for bug report, if you would like to ask a question, 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).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After I added an api-key of Zhipu, my knowledge base and model providers could not be queried, and a network error was reported.

✔️ Expected Behavior

all is right

❌ Actual Behavior

No response

[dosubot]

@tyutltf Hello! I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer.

I found a similar unsolved discussion titled dify internal server error, which might be related to the issue you're experiencing ^[1]. Additionally, there is a closed issue where the suggested solution was to check out the v0.15.3 tag to start it from source, as there is no plugin daemon under version 1.0.0 ^[2].

For your specific issue with the Zhipu API key causing an "Internal Server Error," ensure that the API key is correctly configured and valid. Dify handles API key validation through the validate_credentials method, and if the key is invalid, it will raise a CredentialsValidateFailedError ^[3]. Additionally, make sure the Authorization token is formatted correctly as 'Bearer ' in the Authorization header to avoid 401 or 403 errors ^[4].

If the problem persists, consider checking the logs for any specific error messages that might provide more insight into the issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[crazywoola]

For internal server error, please provide the container logs.

[tyutltf]

对于内部服务器错误，请提供容器日志。

Thanks, where is the path to the container logs?

[crazywoola]

Please read the docs here https://docs.docker.com/?_gl=1*ia4exk*_gcl_au*NDk3MjMyMTgwLjE3NDA3MDc4NzE.*_ga*NjY4NjQzMDQ2LjE3MzIwOTQyNDk.*_ga_XJWPQMJYHQ*MTc0MDcwNzg3MS41LjEuMTc0MDcwNzg3NC41Ny4wLjA.

[tyutltf]

Please read the docs here https://docs.docker.com/?_gl=1*ia4exk*_gcl_au*NDk3MjMyMTgwLjE3NDA3MDc4NzE.*_ga*NjY4NjQzMDQ2LjE3MzIwOTQyNDk.*_ga_XJWPQMJYHQ*MTc0MDcwNzg3MS41LjEuMTc0MDcwNzg3NC41Ny4wLjA.

Thank you, I started dify with docker compose up -d . Which container's log should I check for my error?

[crazywoola]

Please check the logs of api

[tyutltf]

Please check the logs of api

this is my log

[crazywoola]

https://docs.dify.ai/learn-more/faq/install-faq#id-2.-how-to-fix-the-file-not-found-error-in-local-deployment-logs

[tyutltf]

https://docs.dify.ai/learn-more/faq/install-faq#id-2.-how-to-fix-the-file-not-found-error-in-local-deployment-logs

Thanks, that solved my problem