Branding

Row-Template is white-label by default: nothing on the served page names Row-Template. You can add three things of your own, all optional.

With no logo, the page shows a monogram built from the service name — for example Katze-VPN gives K-V. The installer previews it for Latin names; for other scripts the browser computes it.

Change branding

From the manager (one field at a time)

row-template

Choose 2 — Reconfigure branding:

  1  Service name
  2  Support URL
  3  Logo
  4  Template
  5  Reset branding
  6  Reconfigure everything
  0  Back

• Service name — type the new name, Enter to keep the current one, or - to clear it.
• Support URL — keep, change or remove it. An invalid link is refused and asked again.
• Logo — use or replace an image, remove it (back to the monogram), or show what is set.
• Reset branding — clears all three and returns to the default look. It does not remove Row-Template.
• Reconfigure everything — the same as row-template config.

With the config command (all fields)

row-template config

It asks for the three fields in turn, showing the current value. Press Enter to keep a value, or type - to clear it.

From your panel’s own settings (PasarGuard, Rebecca)

PasarGuard and Rebecca keep a subscription title and a support link in their own settings. Row-Template can use them, so you do not type them twice (1.4.0):

• On a fresh interactive install the installer shows them and asks Use them for this page? [Y/n]. Answer Enter to use them — the name and link questions are then skipped — or n to type your own.
• On an existing install, open row-template → 2 — Reconfigure branding → 7 — Use PasarGuard’s (or Rebecca’s) name and support link, or run RT_PANEL_BRANDING=1 row-template config.
• In a script, set RT_PANEL_BRANDING=1. RT_SERVICE_NAME and RT_SUPPORT_URL still win for the field they set.

The panels’ own defaults — the title Subscription and the bare https://t.me/ — are never offered, nor a PasarGuard title that still carries a per-subscriber placeholder such as {USERNAME}, and every value passes the same checks as one you type. The settings are only read, and only from a SQLite database; with MySQL, MariaDB or PostgreSQL nothing is offered.

From a script

Give the values as variables. Fields you do not set keep their current values:

RT_ASSUME_NONINTERACTIVE=1 \
RT_SERVICE_NAME="Aurora VPN" \
RT_SUPPORT_URL="tg://resolve?domain=aurora_support" \
RT_LOGO_PATH=/root/aurora.png \
row-template config

Use RT_SERVICE_NAME="" to clear the name, and RT_LOGO_REMOVE=1 to remove the logo.

Every change is safe to try

A branding change never replaces a working page with a broken one:

1. The current configuration and page are set aside.
2. The new configuration is written, and the page is regenerated from it and validated.
3. Only a page that passes validation is swapped in. On PasarGuard and Rebecca the copy in the panel’s templates directory is replaced as well; the panel’s selection is not touched, and nothing is restarted.
4. If anything fails, the previous configuration and page are restored and the error is shown.

How branding is stored

Your values are kept in config.env in the install directory — /etc/3x-ui/sub_templates/row-template/config.env on 3X-UI, /etc/row-template/config.env on PasarGuard and Rebecca — readable only by root and its group (mode 640):

# Row-Template configuration — generated file. Do NOT source this.
# Values are base64 data, read with grep+base64 and never executed.
RT_CONFIG_VERSION=1
TEMPLATE=row
SERVICE_NAME_B64=QXVyb3JhIFZQTg==
SUPPORT_URL_B64=aHR0cHM6Ly90Lm1lL2F1cm9yYQ==
LOGO_MIME=image/png
LOGO_DATA_B64=iVBORw0KGgo…

• Text is stored base64-encoded and is only ever read as data. The file is never sourced or executed.
• In the page it becomes plain JavaScript string data inside one fixed block, escaped so it can never close the script or add markup. The page then inserts it as text, never as HTML.
• The logo is embedded in the page as a data URI, so it loads with no extra request.

Branding survives everything

Updates, rollbacks, template switches and repairs all keep your branding. A rollback restores an older version of the page, but always with your current branding.