← fix library

CRITICAL Dify: Dify console exposed to the internet

Why it matters

Your Dify admin console is reachable from the internet. If the setup never finished, the first visitor becomes admin and owns every app, prompt and model API key you configured. Even with setup finished, the console and its API sit one phished password away from a stranger.

Fix it — 3 steps

1. If `/console/api/setup` says not_started: finish setup NOW from a private network before anyone else does. The first account created becomes admin.
2. Restrict the console to your network or VPN: firewall the public ports (`sudo ufw deny 80; sudo ufw deny 5001`) and reach it over Tailscale, or put it behind an authenticating reverse proxy.
3. Rotate any model API keys already configured if the console sat open uninitialized: assume they were read.

Verify it’s fixed

curl -m 5 http://YOUR_SERVER_IP:5001/console/api/setup  # should time out / be unreachable from outside

References

• https://docs.dify.ai/getting-started/install-self-hosted/docker-compose