For whom: Administrator.
Required Rights: Panel Administrator; Node with Linked Domain, DNS, and Valid TLS
How it works for the operator
The operator selects the template from the built-in directory, if desired, adjusts the title, description, topic and language, attaches to the node, previews and installs. Further installation and verification are performed as tasks of the agent on the node.1
Choose a template.
The template directory is built into the product and grouped into categories (tools, media, documentation, games, gallery, development, utilities). Templates cannot be changed from the interface - this eliminates the accidental damage to the storefront.
2
Set up and preview.
You can set it up and look at the preview. Preview. in the template gallery opens the showcase in a new tab, at the address of the panel itself, and shows exactly what will be put on the node, and not a simplified layout.The preview renders on the server with no external network calls, so it can not “leak” information to third parties. It opens in the sandbox: a storefront is a whole site with its own scripts, and the sandbox keeps them away from the panel session.
3
Check your readiness.
The panel shows the node readiness checklist (see below). As long as there are unlocked blockers, the installation is rejected.
4
Install and check.
Run the installation - the status goes through “in progress” to “installed” only after the successful report of the agent.
Readiness checklist
Installation is possible only when all blockers are closed:- The node exists and its IP is known.
- The domain is tied to the node;
- The domain DNS indicates exactly the IP of this node;
- TLS certificate is present and not expired;
- the agent is registered, online and supports the function;
- The template is available.
Deployment status
Status “set” is issued after the successful installation task reported by the agent: Possible statuses: not established, waiting, installation, installed, update, error, disabled, blocked by preconditions, drift detected, manual intervention required.Integrity check (verify)
Verification is a read without change: it confirms that the files deployed are in place and (where applicable) that the public HTTPS route does indeed return exactly the page that was deployed. When a deployment diverges, it is marked as “detected drift” rather than being checked silently.What exactly did you confirm?
Verification of local files, internal origin and public web route are different results. For a regular REALITY connection that does not direct web traffic to SelfSteal, you can not require a public 443 to give the template, in which case the result ofverification_limited is possible: the available local data is verified, but the public showcase is not confirmed.
With multiple public logins, the verification must take into account the actual ports and capabilities of the agent. The success of one endpoint does not mean the success of everyone. Statuspage, or subscription pages connected through a managed fallback, checks the corresponding application, not the previous storefront template.
Application and removal of Flow
A new origin is prepared and verified during application; a repeat after an interrupted installation should not require the missing origin to be in good working order in advance. When you change or delete Flow, the dashboard remaps the owner of the runtime and the SelfSteal route. If the operation does not end, disassemble its report and repeat the standard action. Do not manually delete the shared service while other Flow or pages are using it.Verification
Once installed, the deployment is “set” and
verify confirms the validation levels available. If the public route is in the selected topology, it is separately confirmed that it gives the expected page. When the domain is opened, the browser displays the selected storefront site.Rollback
- Removing the cloaking site is idempotent: the removal team is successful, even if the node is already clean.
- Previous versions are saved (by default, several of the latest), so you can return to the previous version.
- Changing the template automatically removes the old storefront before installing a new one.
