Repository navigation
[Bug] Noticed that 1.1.3 was available, while running 1.1.2. Clicked the Update button.... #22
Description
ChannelWatch Support Report
Summary
Noticed that 1.1.3 was available, while running 1.1.2. Clicked the Update button. It seemed to be running normally, but then an error message appeared: Update restart could not be started. The previous runtime remains selected. Pre-update backup: /config/backups/pre-update.v1.1.3.179...
Expected behavior
The update to run to completion and restart the software. I will attempt a manual restart and see what happens, but I have to submit this or start over.
Reporter
Diagnostics
| Field | Value |
|---|---|
| ChannelWatch version | 1.1.2 |
| DVRs configured | 1 |
| DVRs connected | 1 |
| Core status | Running |
| Monitoring | starting: 1 |
| Notification providers | Discord |
| Enabled feature toggles | Channel watching, Disk space, Recording events, Stream counter |
Activity
JefferMC commentedon Sep 26, 2026
To provide additional information to the story.
After this, I clicked on the home icon and I was successfully running 1.1.3.
CoderLuii commentedon Oct 1, 2026
Thanks for the extra detail. v1.2.0 fixes Retry showing a network error when the update restarts the dashboard. It now checks that the application is ready and running the version selected by the update job.
This release needs the v1.2.0 container image; recreate the container with the same
/configvolume and keep any external storage key you already use. I verified upgrade and rollback preserve the settings and key files.I'm keeping this open because the original restart failure is still unexplained. If it happens again after the image update, send a fresh diagnostic report from Help & Feedback → Report a problem before retrying.
JefferMC commentedon Oct 3, 2026
1.2.0 is installed and running. When 1.2.1 comes out, we'll see if the issue repeats.
CoderLuii commentedon Oct 6, 2026
v1.2.1 is available from Settings > Updates on the v1.2.0 image.
If the restart fails again, the update diagnostics now include a safe failure category. That should help narrow down what stopped the restart without exposing raw error details.
I'm keeping this open because the original failure is still unexplained. If it repeats, send a fresh report from Help & Feedback > Report a problem before retrying.
JefferMC commentedon Oct 7, 2026
Unfortunately, 1.3.0 was out before I saw the above notice, so I do not see 1.2.1 available as an option (you may or may not want to address that issue of not being able to upgrade below the current release--it may well be by design).
CoderLuii commentedon Oct 10, 2026
v1.4.1 includes the change that shows a compatible app update separately from a newer container image recommendation. An already-installed older client still uses its old update-selection logic.
For your existing installation, pull the current image and recreate the container with the same
/configvolume and any existing external storage key. Don't delete/config.I'm leaving this open because the original restart failure is still unresolved. The update-selection fix is verified, but it doesn't establish what caused that restart failure.
CoderLuii commentedon Oct 26, 2026
@JefferMC, I reproduced a collision in the older updater: a background restart starts first, then Apply rejects the duplicate request and keeps the dashboard busy until the restart times out.
The handling for that case shipped in v1.6.0 and is included in v1.6.1. It passed the same collision with the older restart helper. I also verified a signed v1.5.3 to v1.6.1 in-app update in one unchanged container, with existing settings and history preserved.
I haven't established that this caused your original failure, so I'm leaving this open. Can you share your current app and image versions from Settings > Updates, and whether the first update attempt still fails? If it does, please send a fresh report from Help & Feedback > Report a problem before retrying.
v1.6.1 release notes
JefferMC commentedon Oct 26, 2026
I seem to have fallen a bit behind. I've updated to 1.6.2. If there's a 1.6.3, I can see what happens.
CoderLuii commentedon Oct 27, 2026
@JefferMC, v1.6.3 is available now. From v1.6.2, open Settings > Updates, check for updates and install v1.6.3. You don't need to recreate your container.
Please let me know whether it completes on the first attempt. If it fails or stalls, send a report from Help & Feedback > Report a problem before retrying so we can capture the failed update state. I'll leave this issue open while we check that.
v1.6.3 release notes
JefferMC commentedon Oct 27, 2026
JefferMC commentedon Oct 27, 2026
CoderLuii commentedon Oct 27, 2026
@JefferMC, thanks for the screenshot. Refreshing the browser reloads the last saved update result; it doesn't run a new update check.
In Settings > Updates, scroll to the bottom of the Update Center card and click Check for updates, below the version/status cards. Wait for the check to finish. If v1.6.3 appears, you can install it there without recreating your container.
If it still says v1.6.2 is current, or the check shows an error, please send a fresh report from Help & Feedback > Report a problem right after the check. Include what the check displayed so we can investigate why v1.6.3 isn't appearing. I'm keeping this issue open.
JefferMC commentedon Oct 27, 2026
CoderLuii commentedon Oct 27, 2026
@JefferMC, thanks for confirming that the in-app update completed and the dashboard restarted on v1.6.3. Closing this now. If the update or restart problem returns, please reopen it with a fresh report.