Repository navigation
Troubleshooting
OhneB edited this page Oct 17, 2026
·
1 revision
| Problem | What to check |
|---|---|
| Requests time out | Try Connection Quality 3 in Settings > Connection if using 1 or 2. It allows 15 seconds to connect and 30 seconds per request. Higher values allow more time. |
| No campaigns | Clear display filters and refresh inventory. If the catalog is down, wait and retry. Relogging or clearing cache will not add missing catalog entries. |
| Mining is idle | Select a game or enable other-game badges/emotes. Check live channels, game-account linking, reward dates, prerequisites and mining filters. |
| Progress is stuck | Compare with Twitch inventory and stop simultaneous manual viewing. Dashboard connected only describes the browser connection. |
| HTTP 401/403 | Reauthorize if Twitch reports an authentication failure. Public-page failures do not invalidate your saved login. |
| Cannot write data or logs | Check folder permissions for the configured UID/GID and that no second miner uses the data directory. |
| Proxy writes or live updates fail | Open the exact PUBLIC_BASE_URL. Check Nginx and both HTTP and WebSocket forwarding using the HTTPS guide. |
docker compose logs --since=30m --tail=200 twitch-drops-minerDetailed server logs are in logs/TDM.*.log, not the Activity page.
If those do not explain the failure, add TDM_DIAGNOSTICS: "true" to the service's
existing environment block and recreate the miner:
docker compose up -d --no-deps twitch-drops-minerFor the server binary, use --diagnostics or TDM_DIAGNOSTICS=true. Diagnostics are off
by default, even with -v or -vv.
Reproduce the problem, review the logs before sharing, then remove the option and restart. Logs may contain account information. Never upload credentials or your data directory.
Include your version, installation method and steps when reporting a bug.