> ## 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.

# Installation of a subscription page

> Selection of server and TLS, verification of proxy, registration and delivery of the page to the client.

Open **Subscription Page → Add** page and choose to create a new one or connect an existing one. In the section, you can store several pages and switch between them. The new installation wizard saves the preparation: you can continue it after you return.

> [!NOTE]
>
> For whom: Panel Administrator Required Rights: `subscription_page.deploy`

## Connecting an existing page

If the Remnawave Subscription Page is already working, select **Connect an existing one**:

1. Set a name, a public HTTPS domain with no protocol and no path, and a Remnawave connection.
2. Wait for the client response and the HTML page to be checked at the public address.
3. If both checks are successful, click **Connect the page**. If you make an error, correct the address or issuance settings and repeat the check.

The connection does not install software, does not change the DNS or Remnawave subscription settings. The page is marked **Connected from the outside**. Axottle monitors availability and certificate; you need to update it on the original server. For personal registration, you need a gateway Axottle: adding an external address record does not set it.

The next steps relate to the **new** installation.

## What do you need?

* Separate server under the page: **Pure** Linux and access via SSH.
* A subdomain, such as `sub.вашдомен.ru`, and the ability to create an A-record for it.
* Open to the outside 80 and 443 on this server: the certificate is issued over HTTP-01, except for the installation behind the already standing proxy, where the TLS is completed.
* Connect to Remnawave with a given API address and token: the page takes subscriptions from there, and without this the wizard will not give.

> [!WARNING]
>
> A separate clean server reduces the dependence of the page on the panel and nodes. Matching is allowed in a supported configuration after checking the owner of the ports. The subscription page is a public site that every client opens: next to the panel or node, it becomes the road to your infrastructure, and on a busy car it rests on someone else's 80 and 443. Why is it — [Why a separate server Z](https://docs.axottle.com/en/subscription-page/overview.md#почему-отдельный-сервер) and [Clean server](https://docs.axottle.com/en/getting-started/requirements.md#чистый-сервер).

## Master's steps

**1. Title:**

You can only see it in the panel, you can't show it to the client, and you can change the name by going back in the steps of the master.

**2. Address**

A domain without `https://` is usually a subdomain of the `sub.вашдомен.ru` type. At this address, the client will open the page and pick up the config.

By "Advanced" is a TLS reminder: by default, the certificate releases itself to the page through Let's Encrypt. If it already has your Caddy or nginx in front of it, it is the certificate responsible for it.

**3. Where to put it.**

There are two ways, and the choice depends on what the master will ask next.

**The panel will run it on SSH itself.** You enter the server address, the port, the user, and one secret: a private key or a password. The details are needed for one installation and are not stored anywhere. The domain must point to the same server.

**I'll put it next to the existing proxy.** Panel issues one command, you run it on the server from root; you don't get access to the server. The page sits on `127.0.0.1` and doesn't answer for the certificate - TLS completes your proxy, so the DNS check step is skipped. Here you ask **port of the** page (`3010` default) - you should change it only if the port is already occupied. Together with the panel gives the finished piece for the configuration for Caddy and nginx.

**4. Combination warning**

It only appears if the selected server is a panel server or a recognized node. The wizard checks both the connection host and the address the domain looks at: they are different for NAT, and any of them can coincide with a known server.

The screen explains what it's going to pay for, and for a few seconds it leaves the confirmation button unavailable. There's no prohibition here, there's a requirement to read.

**5. Domain validation**

The wizard waits for the domain to react to the server, and double-checks it every 15 seconds. You can't miss the step: the certificate is issued on HTTP-01, and unsuccessful release attempts are debited from the Let's Encrypt limit to the domain.

So you're interviewing multiple solvers, and you can see each answer separately: "the panel can't see, but 1.1.1.1 can see" is a diagnosis, and "the domain won't resolve" is a mystery when you write, and the silence of the solver and the answer "there's no such name" are also different.

If the integration with Cloudflare is connected and the desired area is in it, the panel will offer to start an A-record for you. `Zone.DNS:Edit`.

**6. Installation**

It takes a few minutes: the image is swinging, the containers are lifted, the certificate is issued, and you can see the stages along the way.

## Managed proxy on an existing node

If the wizard has identified a compatible node and is managed by SelfSteal, you can use its existing web route. The dashboard checks the owner of the public port and connects the local runtime page; Xray and SelfSteal do not stop to release 443.

For an external proxy, use the domain shown and the actual local port. Don't only connect health-endpoint: the public address must give the web application and the subscription workpage. Re-installation and update must retain the selected topology.

## What Happens During Installation

| Stage | What is done by | |
| - | - | - |
| Readiness Check | Domain, server address and other preconditions | |
| Connect to | Server Checks SSH access, reads OS and architecture | |
| Preparing a disposable key | Released installation key for 15 minutes | |
| Set up a subscription page | Installer: Docker, image, configuration, certificate | |
| Waiting for the page to respond to | The panel goes to the public address and checks that it responds to | |
| Check with Remnawave | Subscription settings are read and checked that the client will receive the page, not the raw | config. |

When installing with your own hands, the panel shows the command and waits: after finishing, the installer will report the panel to the same disposable key.

If the installation fails, the panel shows the last meaningful line of the installer, not the return code. The full output is revealed by the button below the message.

## Placement near Remnawave

With local backend Remnawave, the installer connects the page container to the backend Docker network found. If the external page opens but the subscription does not load, check Remnawave access from the page container, the API address and the installation result. Public HTTP 200 does not confirm this connection.

## Customer and browser verification

Readiness is checked separately for the client to issue a configuration and open a link by the browser.A response from the domain root does not prove that a particular subscription link works.The panel distinguishes between an incorrect public domain, Remnawave rules and a runtime page error.

If the installation is complete and the page delivery is not confirmed, check the report and [link with Remnawave](https://docs.axottle.com/en/subscription-page/remnawave.md). Repeated callback installation should not create a second independent installation; the state is reread by existing operation.

## "Can't bet yet."

The wizard puts everything that's missing in a list and doesn't let the installation run until it's empty.

| Message | What to do with | |
| - | - | - |
| No domain or server address is given to | Return to the address step and fill in | |
| Domain not yet pointing to | server Wait for A-record distribution at | check step |
| No connection to Remnawave | Connect Remnawave panel - [Connect Remnawave](https://docs.axottle.com/en/remnawave/connections.md) | |
| Connections to Remnawave several | Select whose subscriptions show this | page |
| The connection does not have an API address or | token Add them to the connection: without the token, the page will not run | |
| On this server is already a status page Axottle | Take another server: its runtime itself holds 80 and 443 and other sites can not give | |

The button on the screen is a hint, not a resolution: the same list is checked again before the installation key is issued and before the installation itself.

## Verification

> [!TIP]
>
> **Page** shows "Responses", **tile has a deadline,** button **Open page** leads to the work site, and **Card Communication with Remnawave** does not contain warnings. Open subscription page shows the client buttons and QR, not the text of the config.

Immediately after installation, it is normal to see "certificate not yet released": it usually takes a couple of minutes after the domain arrives. The **Check** button rereads the state without waiting for the next five-minute sample.

## Registration and updating of the existing installation

The managed installation includes the Axottle registration delivery component. If the page was installed before this option, open **Manage → Update the** page and execute the issued command on its server. You do not need to install the gateway separately; the external domain, customer links and selected local port are saved.

After you change the Remnawave connection or its API token, update the installation of the page so that it gets the current connection.

If the registration service is unavailable, the gateway retains the original successful Remnawave response, so the availability of the original subscription does not prove that the personalization and issuance rules have been applied.

## After installation

* **Check** - the panel goes to the public address and updates the tiles, including the certificate term.
* **Open the page** Public address in a new tab.
* **Update the page** - fresh image and restart; domain and certificate are not touched. Server access details are not stored by the panel, so it gives a ready command that you execute on the page server yourself.
* **History of operations** What did the panel do with the page and how did it end?

A separate step after installation is the domain of the page in Remnawave itself. Until it is displayed, customers continue to receive links to the old address: the page works, but no one comes to it. [Connection to Remnawave](https://docs.axottle.com/en/subscription-page/remnawave.md#ручной-шаг-домен-страницы-в-remnawave).

## Rollback

* Unfinished wizard is reset with the **Z button to demolish the draft** - it erases the installation draft and returns to the first question.
* The expanded page is removed by the **button Remove from the** panel. The panel stops following it; the page itself continues to work, and the links issued to customers remain working. The server panel cannot demolish — if it is no longer needed, extinguish it with your hands.

> [!WARNING]
>
> Deleting a dashboard entry doesn't revoke links from customers. If a page needs to stop responding, it needs to be deactivated by its server, not the entry in the partition.

## Typical errors

> [accordion] “Domain leads to another address, even though the record is created”
>
> The records take time to disperse. Check that the A-record points to the IP of the page server, not the panel. To check the IP match in the wizard, use DNS only in Cloudflare. When proxies, the solver sees the Cloudflare address; the availability of HTTP certificate verification additionally depends on the route and proxy rules.

> [accordion] Installation terminates at the connection stage
>
> The panel couldn't access SSH. Check the port, the user, and the key fits that server, and the password from the password-free account gives the same failure.

> [accordion] Installer says ports are busy
>
> 80 and 443 are holding something different. Either free them up, or put a page behind that proxy -- I'll put it myself next to an existing proxy, with a pre-built piece of configuration off the panel.

> [accordion] The installation team has expired.
>
> The key lives in it for 15 minutes. Go back to the "I'll put it myself" step and get the command again.

> [accordion] The page responds, but the certificate is not issued
>
> Let's Encrypt checks port 80, which is often closed from the outside, and the second common case is that you've exhausted the limit of failed attempts on the domain, and then you'll have to wait.

> [accordion] Customers are still coming to the old address
>
> Remnawave doesn't display a page's domain. It doesn't go there, it's a variable in the environment of the page's process. The exact value and order of action is [Communication with Remnawave](https://docs.axottle.com/en/subscription-page/remnawave.md#ручной-шаг-домен-страницы-в-remnawave).

> [accordion] The client opens the link and sees a raw config or JSON.
>
> It's about the Remnawave subscription settings, not the page. What to check and what the panel can turn on itself - [Communication with Remnawave](https://docs.axottle.com/en/subscription-page/remnawave.md).

Linked pages: [Subscription page: reviewZ](https://docs.axottle.com/en/subscription-page/overview.md), [Connection with Remnawave](https://docs.axottle.com/en/subscription-page/remnawave.md), [DNS and Cloudflare AutoDNS](https://docs.axottle.com/en/cdn/dns.md), [Clean server ](https://docs.axottle.com/en/getting-started/requirements.md#чистый-сервер).


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