When calling a local large language model through the OpenAI API Compatible plugin in Dify, SSL certificate verification fails.

[jhy1761999]

Self Checks

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

Content

When calling a local large language model through the OpenAI API Compatible plugin in Dify, SSL certificate verification fails. The large language model is deployed in an offline, isolated intranet environment and exposes its service over HTTPS. When Dify attempts to call the local model, an SSL certificate verification error occurs.
Is there a way to configure Dify to bypass SSL certificate verification when calling the local large language model?

[dosubot[bot]]

Hi @jhy1761999! I'm Dosu and I'm helping the Dify team.

The current OpenAI API Compatible plugin does not expose a setting to disable certificate verification. Its LLM client uses the OpenAI SDK without supplying an SSL-verification override. Setting HTTP_REQUEST_NODE_SSL_VERIFY=false is not a workaround for this client: that setting controls the HTTP Request node's transport, not this plugin's OpenAI client. [1] [2]

For a private-CA or self-signed endpoint, the recommended route is to make the issuing CA trusted inside the plugin runtime, rather than disable verification. For a standard self-hosted deployment, start with the plugin_daemon container; trusting the certificate only on the host or in the api container is not sufficient for a separate plugin runtime. Dify's container guidance likewise recommends adding the organization's root CA for private certificate trust. [3]

Could you share your Dify version, OpenAI API Compatible plugin version, and the exact SSL error as text? The certificate error detail will help distinguish an untrusted issuer from a hostname mismatch or an expired certificate.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[jhy1761999]

dify1.10.1
OpenAI API Compatible 0.0.36
The main cause is that the SSL certificate has expired. However, since we are operating in an offline intranet environment, the service administrators recommend bypassing SSL certificate verification altogether.