dify cannot add gemini model key

[liuzhuosin]

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

After I added the gemini model and filled in the key, I found that it couldn't be bound. I guess it's due to network issues, but I couldn't find a good solution. Are there any good ways to solve it?

[liuzhuosin]

@dosu

[liuzhuosin]

I think it's a network issue because when I added the key, I couldn't bind it. How to solve it@dosu

[liuzhuosin]

@dosu

[dosubot[bot]]

Many Gemini model key binding issues in Dify come down to a few main causes: using a deprecated model name (like "gemini-pro"), plugin version bugs, network/proxy misconfiguration (especially in Docker or behind a firewall), or credential schema mismatches.

If you think it's a network issue, check that your Docker/proxy setup allows outbound connections to Gemini endpoints—misconfigured SSRF proxies or using localhost/127.0.0.1 for service endpoints in Docker can block communication. Also, make sure your Gemini plugin version is not one of the known problematic ones (e.g., 0.5.9 or 0.5.7); rolling back to 0.5.6 or upgrading often fixes binding errors (details).

If you can share the exact error message or log from your browser console or server, plus your Dify and Gemini plugin versions and deployment method (Docker, cloud, etc.), I can help you troubleshoot step by step.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[liuzhuosin]

@dosu, could you please tell me how to configure a network proxy for Dify when it is deployed with Docker, so that it can access overseas models?

[dosubot[bot]]

To configure a network proxy for Dify in Docker so it can access overseas models like Gemini, set both uppercase and lowercase proxy environment variables (HTTP_PROXY, HTTPS_PROXY, http_proxy, https_proxy) in your docker-compose.yaml for all relevant services (api, worker, web, plugin_daemon, sandbox). Use your host machine’s local IP address for the proxy URL—do not use 127.0.0.1, as that points to the container’s own loopback interface and won’t work for container-to-host communication. Example:

environment:
  HTTP_PROXY:  http://your_host_local_ip:7890
  HTTPS_PROXY: http://your_host_local_ip:7890
  http_proxy:  http://your_host_local_ip:7890
  https_proxy: http://your_host_local_ip:7890
  NO_PROXY: localhost,127.0.0.1,::1,db,redis,nginx,ssrf_proxy,sandbox,172.*,your_host_local_ip

Add these to each service that needs outbound access. Also, set DNS servers (like 8.8.8.8) in the docker-compose.yaml to help with DNS resolution if needed. If you’re using Dify’s built-in SSRF proxy (Squid), make sure SSRF_PROXY_HTTP_URL and SSRF_PROXY_HTTPS_URL are set to the correct proxy endpoint (e.g., http://ssrf_proxy:3128), and SANDBOX_HTTP_PROXY/SANDBOX_HTTPS_PROXY are set for the sandbox service as well. For WSL2 users, enabling networkingMode=mirrored and autoProxy=true in WSL2 config allows you to use the system proxy without extra Docker config. More details and examples are available in the official discussions and issues and here.

If you run into errors, double-check that your proxy is reachable from inside the container, and that NO_PROXY includes all internal addresses and service names to avoid routing internal traffic through the proxy. Using the latest Dify and plugin versions is also important for successful model binding in Docker environments.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[liuzhuosin]

I solved this problem.
I have added the proxy settings to the api, worker, and plugin_daemon services in the docker-compose.yaml file as follows:
http_proxy: http://xxx:7890
https_proxy: http://xxx:7890
no_proxy: localhost,127.0.0.1,plugin_daemon,plugin-daemon,redis,db,ssrf_proxy,172.18.0.0/16