Cancel & Report
When a QuickBox Pro dashboard job stalls — a stuck app install, a VPN config generation that hangs, an SSL cert that times out — the modal that launched it normally locks until the job finishes. Cancel & Report gives you a way out: stop the job, unlock the modal so you can close it, and optionally send your admins a snapshot of what went wrong so they can investigate.
Cancel & Report is built into the v4 dashboard UI. You do not need to run any terminal commands to use it. If the job is stuck, just look for the “Cancel job” button in the modal header.
What it does
Stops the stuck job cleanly
The running process is stopped gracefully. If it does not stop on its own within a few seconds, it is forcibly terminated. Either way, the job ends.
Unlocks the modal immediately
Once the job stops, the Close button and backdrop click both become active. The "Cancelled" badge appears in orange so you can see what happened at a glance.
Optional report to administrators
Toggle "Report this to admins" in the confirmation dialog to send your message and a sanitized job-state snapshot to all server administrators.
Lets you retry right away
After closing the modal, you can start the same job again immediately. There is no waiting period or manual cleanup required.
Where it appears
Cancel & Report is available inside any of these five dashboard modals when a job is actively running:
| Surface | What it cancels |
|---|---|
| Apps tab — package installs, removals, reinstalls, updates | A stuck app operation (e.g., Sonarr install that hangs on a dependency) |
| VPN Control — WireGuard ops and NordVPN config generation | A VPN config step that hangs, often due to a DNS or network issue |
| SSL Control — certificate operations | An SSL cert job stuck on a DNS challenge or network timeout |
| Dashboard self-update | The dashboard update pipeline if it stalls mid-download or mid-build |
| Per-app updates | An individual app update (triggered from the app’s own update modal) |
The “Cancel job” button only appears in the modal header while a job is actively running. Once the job completes (successfully, with an error, or after cancellation), the button disappears and the modal’s normal close controls take over.
How to use it
Step 1 — Find the “Cancel job” button
When a job is running, look at the top of the progress modal. To the left of the status badge and the Close (×) button, you will see a small red Cancel job button. It is intentionally subtle — it does not compete with the running status — but it is always there during an active job.
Step 2 — Click “Cancel job”
A confirmation dialog opens. The dialog title reflects which subsystem is running (for example, “Cancel this VPN job?” or “Cancel this package job?”) so you can confirm you are cancelling the right operation.
Step 3 — Decide whether to report
The dialog includes an optional “Report this to admins” toggle. When you turn it on:
- A text field appears where you can describe what happened (up to 500 characters).
- When you confirm, administrators receive a notification (in-app, and through whatever channels they have configured — Signal, Discord, or email) containing your message and a sanitized snapshot of the job’s state at the time of cancellation.
Your message and the snapshot are sanitized before sending: plain text only, no passwords or tokens, and the snapshot is capped so it cannot carry sensitive data.
If you leave the toggle off, no report is sent — only the job is cancelled.
Step 4 — Confirm or keep running
The dialog has two buttons:
- Keep running — dismisses the dialog and lets the job continue.
- Cancel job — confirms the cancellation. The job stops, the dialog closes, and you are returned to the progress modal with the orange “Cancelled” status badge.
Step 5 — Close the modal and retry if needed
Once cancelled, the modal’s Close button and the backdrop click both become active. Close the modal and, if the underlying cause is resolved, start the job again from scratch.
Who can cancel a job
Access follows the same rules as the operation that started the job:
Scenario
- Package install, remove, reinstall, or update is stuck
- Your own job — you started it from your account
- Admin viewing any user's stuck package operation
- VPN config generation hangs (admin-only surface)
- SSL cert job stuck mid-challenge (admin-only surface)
- Dashboard self-update stalls (admin-only surface)
Who can cancel
- You can cancel it — job owners can cancel their own package jobs
- You can cancel it — the job owner is always allowed
- Admins can cancel any package job regardless of who started it
- Admin-only — only admins can cancel VPN, SSL, or dashboard-update jobs
- Admin-only — only admins can cancel VPN, SSL, or dashboard-update jobs
- Admin-only — only admins can cancel VPN, SSL, or dashboard-update jobs
In short: package jobs can be cancelled by the account the package is for, or by any admin. VPN, SSL, and dashboard-update jobs are admin-only.
Real-world examples
NordVPN config generation hangs mid-flight
You kick off a NordVPN WireGuard config generation from the VPN Control tab. Halfway through, your server’s DNS resolver goes down. The job hangs indefinitely — it is waiting for a network response that will never come.
With Cancel & Report: Click Cancel job. The generation stops, the VPN modal unlocks. Toggle the report on and describe what you saw (“DNS lookup timed out during NordVPN config step”). Admins receive the snapshot and your note. Once DNS is restored, you can retry the config generation.
Sonarr install stalls on a dependency
You start installing Sonarr from the Apps tab. The install hangs — maybe an apt lock, maybe a slow package mirror. The progress modal is locked and you cannot close it.
With Cancel & Report: Click Cancel job in the modal header. The install process stops cleanly. The modal unlocks with the orange “Cancelled” badge. You can close it and retry the install once the dependency issue clears — no admin intervention needed, no manual cleanup.
WireGuard peer activation hangs
An admin uploads a new WireGuard peer config from the VPN Control tab and starts activation. The activation step hangs because of a network policy conflict.
With Cancel & Report: Admin clicks Cancel job. The activation stops, the modal closes. The admin can investigate the network conflict and retry activation once it is resolved. Toggling the report sends a snapshot to other admins so the team is aware.
SSL cert stuck on DNS challenge
An SSL cert provisioning job is waiting for a DNS challenge to propagate. The propagation is taking longer than expected and the job has not progressed in minutes.
With Cancel & Report: Cancel the job. Retry once you have confirmed the DNS records have propagated (use a tool like dig or an online DNS propagation checker before retrying).
Dashboard self-update hangs
The dashboard update pipeline stalls — for example, the download from the update server times out or a package registry is slow. The dashboard is partially updated and in an inconsistent state.
With Cancel & Report: Cancel the job. After cancellation, run qb fix dashboard from the CLI to re-trigger the full update pipeline cleanly from a known-good state.
If you cancel a mid-flight dashboard self-update, the dashboard may be in a partial state. Run qb fix dashboard to re-run the update pipeline and bring the build back to a consistent state. See Restart or Repair the Dashboard for details.
What the report contains
When you toggle “Report this to admins,” the notification admins receive includes:
- Your message — exactly what you typed (500 chars max, plain text).
- A sanitized job snapshot — the job’s subsystem, the action that was running, and its state at the time of cancellation.
What is not included: passwords, API keys, tokens, user credentials, or any sensitive identifying information. The snapshot is automatically sanitized and capped before it is sent.
Admins receive the report through whichever notification channels they have enabled in their settings (in-app notifications, Signal, Discord, or email).
If the issue was transient (network hiccup, slow mirror) and you do not need admin awareness, just leave the toggle off and confirm. The job stops and the modal unlocks — no report sent.
Best practices
Do
- Check the job log in the modal before cancelling — sometimes a job finishes on its own given a moment.
- Use the report toggle when the failure seems unusual or you want admins to know about it.
- After cancelling a stuck install or update, wait a moment before retrying — let any background processes finish.
- After cancelling a stuck dashboard self-update, run
qb fix dashboardbefore retrying via the dashboard UI. - Include a clear description in your report message so admins have context ("DNS lookup timed out during NordVPN step at ~14:30").
Don't
- Cancel a job just because it is taking longer than expected — some operations (large installs, cert provisioning) are legitimately slow.
- Cancel and immediately retry if the underlying cause has not changed — the same job will get stuck again.
- Ignore the orange "Cancelled" badge — it means the job did not complete and the operation may need to be retried.
- Try to manually stop the underlying process via terminal while the dashboard job is running — use Cancel & Report instead so state is cleaned up properly.
FAQ
The cancellation is confirmed once the job transitions to the "Cancelled" state (orange badge). If the modal stays locked after you confirm in the dialog, wait a few seconds — the job is being stopped cleanly and the UI updates as soon as the process ends. If it stays locked for more than 30 seconds, try a hard refresh of the dashboard page.
No. QuickBox job cancellation stops the running process and marks the job as aborted. Partially installed files may be on disk, but the package is not registered as installed in your dashboard. Running the install again from scratch will start fresh. If you are concerned about leftover files, an admin can use qb reinstall <software> to do a clean install.
For package operations (installs, removes, reinstalls, updates) — the user whose account the package belongs to can cancel their own job. Admins can cancel any package job. For VPN, SSL, and dashboard-update operations, only admins can cancel.
The report goes to all server administrators as a notification. It contains your message (plain text, 500 chars max) and a sanitized snapshot of the job state — no passwords, no tokens, no sensitive credentials. Admins receive it through whatever notification channels they have configured: in-app, Signal, Discord, or email.
Yes. The text field shows a live character count and disables the confirm button once you go over 500 characters. Trim your message until the counter goes green, then confirm. A focused description is usually more useful than a long one anyway.
No — orange means the job was intentionally cancelled by a user, not that something went wrong on the system side. Red means the job failed on its own. Orange means you stopped it on purpose. You can close the modal and retry from scratch whenever you are ready.
The button only appears while a job is actively running. If the job has already finished (succeeded, failed, or was previously cancelled), the button is not shown. Also confirm you have access to cancel: for VPN, SSL, and dashboard-update jobs, you need admin access. For package jobs, you need to be either the job owner or an admin.
Run qb fix dashboard from the CLI. This re-runs the full dashboard update pipeline and rebuilds to a clean state. It is safe to run and preserves all your settings and user data. See Restart or Repair the Dashboard for step-by-step instructions.
If the job has already reached a terminal state (failed, succeeded, or previously cancelled), the job is no longer running — the modal close-lock will already be relaxed and you can close it normally. Cancel & Report is specifically for jobs that are stuck in a running state.
Related references
More troubleshooting resources
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.