Troubleshooting CookDex
| Problem | Fix |
|---|---|
| Weak master key warning | Set a stronger MO_WEBUI_MASTER_KEY in .env, or let CookDex auto-generate one. See how secrets are stored. |
| 401 on login (cookie not sticking) | Set WEB_COOKIE_SECURE=false in .env |
| Port already in use | Set WEB_BIND_PORT=4821 in .env |
| Tasks page shows no tasks | Ensure the server started without errors; check the container log with docker compose logs cookdex |
Test Mealie fails with localhost |
Inside the CookDex container, localhost is the container itself. If CookDex and Mealie share a Docker network, use the Mealie service name, such as http://mealie:9000. See Getting started. |
| Database connection can’t be reached | Jobs fall back to the API with a warning in the log. See which host to use. |
After an update, confirm you can log in and check https://localhost:4820/cookdex/api/v1/health.
Still stuck?
Section titled “Still stuck?”- The Help page inside CookDex documents every task and setting in place.
- Bugs and feature requests: open an issue.
- Running from source? See the troubleshooting table in Local Dev.