How to solve the problem of Control server error: [Errno 13] Permission denied

[yanpx169]

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

Deploy version 1.14.2 on the new server using docker compose，error info:
api-1 | [2026-06-08 12:24:53 +0000] [1] [ERROR] Control server error: [Errno 13] Permission denied: '/home/dify'
api_websocket-1 | [2026-06-08 12:24:53 +0000] [1] [INFO] Starting gunicorn 26.0.0
api_websocket-1 | [2026-06-08 12:24:53 +0000] [1] [INFO] Listening at: http://0.0.0.0:5001 (1)
api_websocket-1 | [2026-06-08 12:24:53 +0000] [1] [INFO] Using worker: geventwebsocket.gunicorn.workers.GeventWebSocketWorker
api_websocket-1 | [2026-06-08 12:24:53 +0000] [110] [INFO] Booting worker with pid: 110
api_websocket-1 | [2026-06-08 12:24:53 +0000] [1] [ERROR] Control server error: [Errno 13] Permission denied: '/home/dify'

docker file directory location: home/dify/dify-1.14.2/docker,
data storage directory: home/dify/volumes

root@yan:/home/dify# ls
dify-1.14.2 dify-1.14.2.zip images volumes volumes-260531backup.tar
root@yan:/home/dify# cd dify-1.14.2/
root@yan:/home/dify/dify-1.14.2# ls
AGENTS.md CLAUDE.md depot.json docker eslint.config.mjs LICENSE packages README.md vite.config.ts
api codecov.yml dev docs eslint-suppressions.json Makefile pnpm-lock.yaml scripts web
AUTHORS CONTRIBUTING.md dify-agent e2e images package.json pnpm-workspace.yaml sdks
root@yan:/home/dify/dify-1.14.2#

[dosubot[bot]]

This is a known issue with gunicorn 25.x+ in Dify's Docker containers. Gunicorn now enables a control socket by default that requires a writable HOME directory, but /home/dify doesn't exist inside the container, causing the [Errno 13] Permission denied: '/home/dify' error [1].

Fix: Create a docker-compose.override.yaml file in your home/dify/dify-1.14.2/docker directory:

services:
  api:
    environment:
      - HOME=/tmp
  api_websocket:
    environment:
      - HOME=/tmp
  worker:
    environment:
      - HOME=/tmp

Then restart:

docker compose down
docker compose up -d

After this, you should see Control socket listening at /tmp/.gunicorn/gunicorn.ctl in the logs instead of the permission error [1].

Note: While this error looks alarming, in some deployments it's non-critical and the API still functions. However, in other cases it can cause the gunicorn worker to silently die, resulting in 502 errors. The HOME=/tmp fix resolves it reliably [2].

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[yanpx169]

@dosu You're awesome, thank you

[dosubot[bot]]

You're welcome! Glad I could help. If you run into any other issues with your deployment, feel free to ask. 🙂

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.