Troubleshooting
docker compose: command not found
Issue: Docker is not installed or not in your PATH.
Solution: Install Docker Desktop and make sure it is running. Restart your terminal after installation.
Error: Docker is not running
Issue: Docker is installed but not running. WordPressify checks for Docker before executing any Docker command and shows this error if it is not available.
Solution: Open Docker Desktop and wait for it to fully start before retrying the command.
Bind for 0.0.0.0:3020 failed: port is already allocated
Issue: The default port is already in use by another process.
Solution: Change the port in your .env file to a different value, e.g. PROXY_PORT=3030, and restart.
403 Forbidden or 502 Bad Gateway after starting
Issue: WordPress and the build tools are still initializing.
Solution: Wait 10-20 seconds for the containers to finish setting up, then reload the page.
File changes are not detected (Windows)
Issue: The file watcher does not work with the default settings on Windows.
Solution: Set USE_POLLING=true in your .env file. See the Windows Installation page for details.
Node.js version mismatch errors
Issue: Your local Node.js version is incompatible with the project dependencies.
Solution: Use Node.js 18 or later. If you do not want to install Node.js locally, run everything through Docker with docker compose up.