Troubleshooting
If Sublarr isn’t behaving, start with General Troubleshooting — most issues come from a missed bootstrap variable, a path that isn’t mounted, or a blocked outbound provider request. The other pages cover narrower topics.
General Troubleshooting Symptom → cause → fix for the most common issues.
Performance Tuning Large libraries, translation throughput, scan intervals.
Reverse Proxy nginx, Caddy, Traefik, NPM — TLS termination and headers.
Where to look first
Section titled “Where to look first”| Symptom | Look here |
|---|---|
| Container doesn’t start | docker logs sublarr for the first error line. |
| UI loads but nothing happens | Browser DevTools → Network for HTTP 4xx/5xx. |
| Subtitles never download | Settings → Providers → check enabled + healthy. |
| Translation jobs stall | Settings → Translation → backend test + queue dashboard. |
| Disk fills up | Cleanup + Trash — old .bak files and soft-deleted sidecars. |
| Scheduled job didn’t run | Settings → System → Scheduler → history tab. |
If you don’t find your symptom on these pages, open a GitHub issue with the relevant docker logs excerpt.