Failed to request plugin daemon

[zt-x]

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

1.4.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I followed the instructions in the ReadMe exactly, using the Docker deployment.
My platform is Ubuntu 22.04，on Jetson Orin NX 16G
It's work in the same step when i do this on my own computer with Exactly same steps，
but when I try it on my Jetson Orin，it failed.

I configured the Docker Daemon with the clash vpn on Jetson Orin, and I don't know if this will make a difference

I have tried to close my vpn，but it also doesn't work、

✔️ Expected Behavior

no error alert

❌ Actual Behavior

I can browse“Model market”, but I can't install them and report errors

if I copy this link and visit it on my browser, I can download this model, so I am sure my internet is connected

[TheEterna]

Has it been resolved

[zt-x]

Nope :(

[Skure1027]

启动前的配置文件名是.env吗，我把名字从.env改为了middleware.env，这个错误就消失了

[zt-x]

when I use
docker compose up
to start it，

got an error on the console

ProxyError('Unable to connect to proxy', NewConnectionError('<urllib3.connection.HTTPConnection object at 0xffff5a116480>: Failed to establish a new connection: [Errno 111] Connection refused')))
api-1 |
api-1 | During handling of the above exception, another exception occurred:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 64, in _request
api-1 | response = requests.request(
api-1 | ^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/requests/api.py", line 59, in request
api-1 | return session.request(method=method, url=url, **kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/requests/sessions.py", line 589, in request
api-1 | resp = self.send(prep, **send_kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/requests/sessions.py", line 703, in send
api-1 | r = adapter.send(request, **kwargs)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/.venv/lib/python3.12/site-packages/requests/adapters.py", line 694, in send
api-1 | raise ProxyError(e, request=request)
api-1 | requests.exceptions.ProxyError: HTTPConnectionPool(host='127.0.0.1', port=7890): Max retries exceeded with url: http://plugin_daemon:5002/plugin/fd0050c2-d1d4-478a-a79b-d13231051d68/management/install/tasks?page=1&page_size=100 (Caused by ProxyError('Unable to connect to proxy', NewConnectionError('<urllib3.connection.HTTPConnection object at 0xffff5a116480>: Failed to establish a new connection: [Errno 111] Connection refused')))
api-1 |
api-1 | During handling of the above exception, another exception occurred:
api-1 |
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/plugin/impl/base.py", line 140, in _request_with_plugin_daemon_response
api-1 | response = self._request(method, path, headers, data, params, files)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/app/api/core/plugin/impl/base.py", line 69, in _request
api-1 | raise PluginDaemonInnerError(code=-500, message="Request to Plugin Daemon Service failed")
api-1 | core.plugin.entities.plugin_daemon.PluginDaemonInnerError

[caobaoqi6040]

I encountered the same problem as you —— api-1 | requests.exceptions.ProxyError: HTTPConnectionPool(host='127.0.0.1', port=7890):

I deleted the proxy configuration in vim ~/.docker/config.json and restarted the docker service

• systemctl daemon-reload
• systemctl restart docker

I then redeployed dify. Here are my steps:

1. Delete the volumes directory under <your_dify>/docker (proceed with caution)
2. Clear any remaining docker network dependencies

P.S. I am using dify 1.7.1 and Ubuntu 24.04

[dfxbb]

After upgrading Dify from 1.4.1 to 1.5.1, I encountered the same issue.

I noticed that the docker-plugin_daemon-1 container kept restarting, reporting error that S3_USE_AWS was empty, whereas a boolean value is expected.

The problem is likely the absence of the PLUGIN_S3_USE_AWS variable in the .env file (when upgrading from an older version), and the default value of S3_USE_AWS in docker-compose.yaml is empty instead of "false".

The fix is to add PLUGIN_S3_USE_AWS=false to the .env file.

[liulunet]

I encountered the same issue. The cause in my case was that the Docker host had a network proxy enabled, and this proxy configuration was inherited by the dify-api container. You can verify this by running docker compose exec api env | grep -I proxy. Ultimately, I resolved the issue by configuring the environment section for the api service in the docker-compose.yaml file:

services:
  # API service
  api:
    image: langgenius/dify-api:1.7.2
    restart: always
    environment:
      # Use the shared environment variables.
      <<: *shared-api-worker-env
      HTTP_PROXY:
      HTTPS_PROXY:
      http_proxy:
      https_proxy: