Skip to main content
Statuspage is updated regardless of the Axottle bar. Open Status page → Deploy: This shows the installed and available version of the page application. The release directory error is displayed separately from the lack of updates.

Before the update

Check your existing server, domain, and page affiliation to the panel, and keep a backup of Statuspage data and configurations on its server. Updating the panel does not, by itself, update the page app. For official reading of the states of components of a closed page, runtime Statuspage v0.1.8 or newer is required. Check also the compatibility of the necessary design settings with the runtime installed.

Update to SSH.

  1. Check out the stable version available.
  2. Select Update to SSH and enter one-time details of the existing server.
  3. Confirm the update and wait for the completion of the stages.
  4. Check the running version, communication with the panel and publication of accumulated changes.
The details of this operation are not stored. The installer checks the checksum and the binary version before being replaced, saves the data and enrollment.

Update the team

Choose. Get an update commandRun it on an existing server, then press it. Check the installationThe command fixes the selected version. Receiving it does not trigger the update. Check the installation It only checks the connection and does not download the new version.

Verification

Separately check the runtime version, dashboard connection, published revision, and fresh component states. Open the Regular Visitor Rights page: Publication status and service availability — different checks. For an old public runtime, the dashboard can use a compatible public summary in the absence of a new service method. Authorization or communication error is not replaced by this backup method. If the closed page does not give a state, first check the runtime version and anchor.

Rollback

A regular update does not serve as a downgrade button. If you fail, check the install log and the actual running version; do not consider receiving a command as a successful update; Restore data and the previous installation from a prepared backup with compatibility check. Recreate the page is not required for a regular update and may break the existing binding. The availability of features depends on the version installed; code verification is not a substitute for checking your infrastructure.