-
Notifications
You must be signed in to change notification settings - Fork 3
Diagnostics
Open Settings > Diagnostics to inspect the running Pinchflat-ngx instance.
- Confirm that the container is healthy with
docker compose ps. - Review recent output with
docker compose logs --tail 200 pinchflat-ngx. - Open Settings > Diagnostics and run the relevant integrity checks.
- Check the queue diagnostics for running, retryable, or discarded jobs.
- Record the Pinchflat-ngx image tag and yt-dlp version.
Remove client secrets, cookies, tokens, local paths, and private media details before attaching logs to an issue.
The queue diagnostics page can reset or cancel individual jobs and clear discarded queues. Read the job's error before changing it: repeated authentication, rate-limit, or filesystem errors usually need their root cause fixed first.
Lower download concurrency in Settings if YouTube rate-limits the server. Rate-limit and similar bot-challenge
responses are treated as transient download failures, not as a permanent download block. If a
YT_DLP_*_WORKER_CONCURRENCY environment variable is set, it overrides the interface until removed.
On Home and source media tables, Retry Now retries a transient failure. Force Retry can attempt a permanent failure. Failed history can be filtered by All, Transient, or Permanent.
Settings > Diagnostics includes a PO-token provider card. With POT_PROVIDER_URL unset, the provider is disabled
and yt-dlp arguments stay unchanged. When a URL is set, use Test Provider to hit the provider's bounded /ping
endpoint. The UI never displays tokens.
Use the repository's bug report form for Pinchflat-ngx-specific regressions. Use the Upstream Pinchflat wiki for behavior shared unchanged with upstream.