Applying Panel Self-Updates

MyOsicam includes a built-in self-update mechanism. When a new release is available, a banner appears inside the panel. You can apply the update directly from that banner — the panel downloads the signed release archive, verifies its integrity, and swaps the panel files in place. An audit log records every check and apply attempt.

When an update is available

The panel checks for new releases automatically (the check runs as a cron job, by default hourly at minute 7). When a new release is detected, an Update available banner appears at the top of every panel page.

The banner shows:

• The version number of the available release (e.g. 1.7.3).
• Your currently installed version (shown in parentheses).
• An Apply update button.
• The release title and formatted release notes, if the operator who published the release attached them (see Release Notes).

Note

The update check runs on the cron schedule (/etc/cron.d/myosicam-panel). If you want to trigger an immediate check, you can force a refresh by visiting the Settings area of the panel or waiting for the next scheduled run.

Applying an update

1. When you see the Update available banner, read the release title and notes if present — they describe what the update contains.
2. Click Apply update.
3. A confirmation dialog appears. It repeats the version number, the release title, and the release notes (if any), alongside a note that the panel will restart during the update.
4. Confirm the update.

The update process then:

1. Downloads the signed release archive from the update server.
2. Verifies the archive’s signature and integrity (SHA-256 checksum).
3. Extracts the new files in place.
4. Restarts the PHP-FPM service to activate the new code.
5. Writes a row to the panel’s update audit log recording the outcome.

What happens during the update

• OScam on your servers is not affected. The update restarts only the panel’s PHP-FPM process, not the OScam service or the agent.
• The agent continues sending heartbeats. Any heartbeats received while the panel is restarting are queued and processed once the panel is back online.
• The update takes a few seconds. Your browser will show the panel as temporarily unavailable and then refresh once PHP-FPM restarts.

Caution

Do not close the browser or navigate away while “Applying…” is shown. The update process runs on the server and will complete regardless, but you will not see the outcome message if you navigate away.

Checking update history

Every update check and every apply attempt is recorded in the panel’s audit log:

1. In the sidebar, click Logs.
2. Filter by event type for update-related entries to see the history of checks and applies, including the version that was applied and whether the apply succeeded.

Dismissing the banner without updating

To dismiss the update banner temporarily without applying the update, click the × (dismiss) button on the right side of the banner. The banner will reappear on the next page load or the next time the panel checks for updates.

Troubleshooting update failures

If the update apply fails, the panel attempts to leave the existing installation intact. Check the Logs section for the failed apply event and its error message.

Common causes:

Symptom	Likely cause	Fix
”Signature verification failed”	The downloaded archive was corrupted or tampered with.	Dismiss the banner and try again; if it persists, contact support.
”Permission denied during extract”	The www-data user cannot write to the panel directory.	Check file ownership on the panel root; re-run chown -R www-data:www-data <panel-root>.
Panel does not come back after restart	PHP-FPM failed to restart.	On the server, run sudo systemctl restart php8.3-fpm and check journalctl -u php8.3-fpm -n 50.

Related pages

• Release Notes — what the release notes banner shows and how to read it.
• Troubleshooting / FAQ — general help for panel issues.
• Install the Panel — reference for the original panel installation.