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

# Linking a page to Remnawave

> Browser Issue, Response Rules, Balanced Flow Settings, and Public Subscription Domain.

The subscription page is tied to a single Remnawave connection. If you have multiple connections, select the one you want; if you remove the attached connection, reset the connection.

## What checks the panel

| Test | What is |
| - | - |
| Setting up a | webpage Whether a customer can redirect to a subscription page. Different versions of Remnawave have different fields. |
| Browser Response Rule | Whether a normal HTML query falls into the `BROWSER` rule, rather than being intercepted by an earlier unconditional rule. |
| `serveJsonAtBaseSubscription` | Whether JSON issuance is required by the applied balancing Flow. |
| Live Delivery | Does the client receive the config and the browser receive the page from a real link. |

Having a field or switch on does not replace a delivery check. Older Remnawaves without `responseRules` are not considered broken just because of the lack of this API.

## Settings correction

The check itself does not change Remnawave. Perform the proposed fix action separately and read which setting it changes.

For supported versions, it is possible to restore the **Browser Subscription** system rule before the general response rules, while maintaining user rules and other settings, this is a separate action, not a side effect of opening the page.

The `serveJsonAtBaseSubscription` option required by running Flow should not be turned off for the sake of the browser: this can disrupt the balanced output. If the owner is present, the panel shows it; if the owner is not identified, the setting also does not change automatically.

## Page Domain in Remnawave

Check `SUB_PUBLIC_DOMAIN` in the Remnawave environment: it must match the address of your subscription page, such as `sub.example.com`. After manually changing the environment, a regular Remnawave restart is required.

An incorrect domain can leave runtime pages intact, but send customers back to their previous address, in which case reinstalling the page does not eliminate the cause.

## Personal settings and several pages

V. **Subscription page** First, select the desired instance. Its domain, certificate and history are all relevant to this page; [decoration](https://docs.axottle.com/en/subscription-page/presentation.md) and [pronouncement](https://docs.axottle.com/en/subscription-page/announcements.md) refer to the selected Remnawave connection and shared to its pages.

The gateway of the managed page receives the original Remnawave subscription and applies the design and issuance rules. The settings do not change the subscription period, traffic and user keys. When you change the connection or API token, update the installation of the page. Connecting the external page only registers it for observation and does not change the way it is displayed.

## Verification

Update the integration card, check its output and live delivery. Open the test link in the browser and in the supported client: the browser should get the page, and the client - the suitable configuration of the desired Flow.

## Rollback

Before you manually change your Remnawave settings, keep their previous values. When you return, consider the owners of the settings: adjust the balance setting to the Flow settings used. Then recheck both the browser and the client.

Check the availability of features in the installed assembly.


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