Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
After deploying Dify with Docker, the web container kept restarting and the local install page never loaded. The nginx container logs showed emerg bind() to the all-interfaces address on port 80 failed (98: Address already in use). Something on the host was already using port 80, so nginx could not start and the page stayed unreachable.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
This was a bug in the 0.6.12 release that the team fixed in 0.6.12-fix1 the same day, so the fix is to upgrade: git pull the latest code, docker compose pull, then docker compose up -d. One reporter confirmed the services came up correctly after pulling the fix. If you still see the restarting containers after pulling, double check you actually re-pulled the images and didnt keep a stale docker-compose.yaml. Source: https://github.com/langgenius/dify/issues/5769
Shows how to fix can't reach YOUR_HOST/install after deploying Dify with Docker (nginx restarting). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes pdf2image 'Unable to get page count.
Shows how to fix langflow components panel is empty after install (blank sidebar and canvas). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.