> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Setting up a status page

> SSH, manual installation, existing proxy, registration and verification of this public page.

Open **Statuspage** and go through the installation wizard. You will need the `statuspage.deploy` right, the domain and server. A separate server helps the page to remain accessible if the panel fails.

## Choice of accommodation

| Variant | Who accepts HTTPS |
| - | - |
| Separate server with ACME | Installer prepares certificate and public route.Domain must point to server, ports 80/443 must be available. |
| Existing external Caddy or nginx | You configure the route by configuration fragment from the wizard; runtime page runs locally. |
| Compatible Node with Managed SelfSteal | Axottle checks the owner and readiness, then connects the page as a web route through the existing configuration. |

If the owner is unknown or the configuration is incompatible, eliminate the cause or select the supported mode of the external proxy. To start, it is easier to [separate clean server](https://docs.axottle.com/en/getting-started/requirements.md#чистый-сервер).

## Installation steps

1. Set the name and domain without `https://`.
2. Select the server, installation method, and TLS. For an external proxy, prepare the route shown to the actual local port of the page.
3. Check the DNS and the preconditions. Read the resolvers' answers: no record and timeout are different reasons.
4. When SSH-installation, specify temporary details; when manual, execute the generated command with a one-time key.
5. Wait for the runtime registration and the first photo to be published.
6. Check the public domain and the delivery result of settings.

The manual installation command contains a temporary key. If the deadline has expired or another server is selected, release the current command in the wizard. Don't publish it in logs and support calls.

## Installation for proxy

In `proxy` mode, runtime listens to `127.0.0.1:8088` by default, and an existing proxy completes TLS. The management service address and the public web route are different addresses; use the values from the wizard.

With SelfSteal managed, the panel connects the route after runtime preparation, keeping Xray and the owner of the public 443.Reinstallation and deletion must take this route into account: deleting the record first disconnects the managed fallback, rather than freeing the port by stopping someone else's service.

## What counts as readiness

Successful registration does not mean that the visitor sees the correct page: the panel checks the identity of the public response Statuspage, the web application and its resources; the HTTP 200 response from someone else's site or only the available service health-endpoint does not confirm the completion of the installation.

Publishing is a separate step. If it fails, runtime may already be installed and changes have not yet been delivered. Check the status of the publication and repeat delivery; do not reinstall a serviceable server just because of a pending image.

## Re-installation and disposal

After an error, read the last stage and the full report, then repeat the operation from the dashboard. Use the current keys and the current proxy topology.

Deleting the page in the dashboard removes its settings, components, incidents, and access keys. Runtime itself on the server continues to work. In a managed fallback, it is first disconnected; if it fails, the record is saved for retry. Complete deletion of runtime from the server is a separate operation.

## Page application version

After installation, further updates are performed separately from the panel: [update Statuspage](https://docs.axottle.com/en/statuspage/updates.md). Communication with runtime, publishing settings and fresh state components are checked separately.

## Verification

Open the public address: it is the status page and current published data that should load. In the panel, check registration, runtime availability, delivery time and no pending publishing errors.

## Rollback

If only the external proxy is changed, restore the saved configuration. For managed placement, use the regular route disconnect operation. Remote page settings are restored from the backup; a normal runtime reinstallation does not return deleted components and incidents.

Check the availability of features in the installed assembly.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.