Wiki

Troubleshooting

Container starts but UI is not reachable

Checklist:

1. Confirm container is running: docker ps.
2. Confirm port mapping (-p 8080:80 or your custom mapping).
3. Open http://localhost:8080 (or mapped host/port).
4. Check logs: docker logs dmjbot.

Stuck on login/config flow

• If first-run setup is incomplete, DMJBot redirects to /config/.
• If session is missing/expired, protected pages redirect to /login/.
• Complete setup first, then sign in again.

Model loading or verification fails

• Recheck provider API key and selected model.
• For self-hosted providers, verify host/base URL reachability from inside container network.
• Retry via Settings -> Models.

Tool server connection fails

• Verify transport and endpoint URL.
• Check server container/network accessibility.
• Use verify endpoint in Settings before saving.
• Inspect /api/servers and /api/tools after changes.

File upload problems

• Confirm upload size is reasonable.
• Check allowed extension configuration.
• Check free disk space in mounted /data volume.
• Check logs for multipart upload errors.

WebSocket disconnects

• Ensure reverse proxy forwards WebSocket upgrades correctly.
• If TLS is enabled, use wss:// in browser context automatically.
• Refresh token/session by signing in again when needed.

Data persistence issues

• Always mount /data to a Docker volume or host directory.
• Without a mounted volume, DB/files are lost when container is recreated.