WhiteDNS Panel 0.5.0 — Cotten and backup domains

WhiteDNS Panel 0.5.0

• Soar and Cotten are available in the same panel and subscription, with shared account quota, expiry, speed and connection limits. Existing Soar accounts and links are preserved.
• Add up to eight independent tunnel domains and choose a preferred domain without recreating accounts. DNS checks prove the response came from this server. Each domain and engine receives a stable subscription profile.
• Add up to eight HTTPS panel addresses, prepare certificates before applying changes, and retain the old address when replacing the primary domain. Alternative subscription URLs are shown alongside the main URL.
• The installer keeps the same questions and automatically checks both engines. Fixed UFW access under the existing systemd sandbox and required the maintenance service to respond before reporting installation success.
• Fixed custom resolver ports, resolver failover, concurrent resolver snapshots and the initial Cotten DNS reply. Both UDP and TCP DNS listeners are supported.

Install or upgrade using the existing command:

bash <(curl -fsSL https://raw.githubusercontent.com/WhiteDNS/Soar-Server/main/panel-setup.sh)

Keep UDP/53 and TCP/53 open in the VPS provider firewall. After adding backup domains or enabling Cotten on an existing account, refresh the subscription in WhiteDNS. Save alternative panel and subscription addresses before the current domain becomes inaccessible. This server release does not include a rebuilt Android APK or promise automatic client failover.

Step-by-step Persian installation · Backup domain setup · VPS validation and limits

WhiteDNS Soar Panel 0.4.1 — Form spacing fixes

اصلاح فاصلهٔ فیلدها و دکمه‌های پنل

• کادر رمز و دکمهٔ نصب نسخهٔ جدید در سطرهای جدا و با فاصلهٔ مناسب قرار می‌گیرند.
• همین مشکل در فرم دامنه و امنیت نیز اصلاح شد؛ فاصلهٔ عنوان و ورودی در فرم‌ها و پنجرهٔ لینک/QR یکسان شد.
• تمام صفحات و پنجره‌های حساب و اشتراک‌گذاری در ۲۰۰ حالت فارسی/انگلیسی، روشن/تیره و عرض‌های ۳۲۰ تا ۱۴۴۰ پیکسل بررسی شدند.

از «به‌روزرسانی پنل» نسخهٔ جدید را نصب کنید و سپس صفحهٔ مرورگر را یک‌بار تازه‌سازی کنید تا ظاهر جدید بارگذاری شود. حساب‌ها و تنظیمات حفظ می‌شوند.

WhiteDNS Soar Panel 0.4.0 — Admin credentials and bulk deletion

تغییر اطلاعات مدیر و حذف گروهی حساب‌ها

• در «حساب مدیر»، نام کاربری، رمز عبور یا هر دو را با تأیید رمز فعلی تغییر دهید. برای حفظ رمز فعلی، فیلد رمز جدید را خالی بگذارید. پس از ذخیره، همهٔ نشست‌های مدیر بسته می‌شوند و باید دوباره وارد شوید.
• در «حساب‌های کاربری»، چند حساب یا همهٔ نتایج فعلی جست‌وجو را انتخاب و با تأیید نهایی حذف کنید. حساب‌ها، کلیدها و لینک‌های ساب انتخاب‌شده با هم حذف و اتصال‌های آن‌ها بسته می‌شوند. حذف برگشت‌پذیر نیست. با تغییر جست‌وجو یا فیلتر، انتخاب پاک می‌شود.
• هر دو قابلیت در رابط فارسی/انگلیسی، روشن/تیره و موبایل در دسترس‌اند.

ارتقا: از داخل پنل، «به‌روزرسانی پنل» ← «بررسی نسخهٔ جدید» ← «نصب نسخهٔ جدید». حساب‌ها، رمز مدیر، لینک‌های موجود و تنظیمات حفظ می‌شوند؛ حذف حساب تنها پس از انتخاب و تأیید خودتان انجام می‌شود.

نصب تازه و راهنمای پاسخ به پرسش‌های ترمینال: https://github.com/WhiteDNS/Soar-Server/blob/main/docs/PANEL.fa.md

WhiteDNS Soar Panel 0.3.1 — Installer fixes

WhiteDNS Soar Panel 0.3.1 — Installer DNS and connectivity checks

Fresh installations now verify the parent A/NS records before starting the
service, then check child SOA and authenticated HTTPS through both the local DNS
listener and recursive resolvers after startup. Missing records cannot be
bypassed with CONTINUE. Failed checks offer retry, resolver changes, rollback,
or an explicitly unverified installation that exits with a nonzero status.

Authoritative DNS uses addresses resolved through the selected resolvers,
retries UDP and falls back to TCP. Errors identify the server, record and
transport. Existing conflicting delegations and stale child DS remain blocked.
The wizard can install missing network tools, accepts corrected input, uses the
default-route local address, and keeps public IPv4 separate on NAT hosts.

Active UFW gets the reviewed UDP/53 rule as well as direct-management TCP when
needed. Existing broad allow rules are preserved; rollback removes only newly
added rules. Provider firewall and NAT rules still need provider-side setup.

A reserved, quota-limited account performs installation checks without using
customer keys or usage. It is removed before completion, expires after an
interruption, and is renewed if an interactive retry takes longer. Rollback
restores database, access settings, helper binaries, units and service enable
states. Reinstalling keeps existing account keys, usage and saved tuning.

Rerun the guided installer to apply installer/firewall changes to an existing
server. An in-panel binary update alone does not rerun the installation wizard.
Passing server-side checks does not guarantee a working DNS path on every phone
network; test the exported account on the intended network.

Validation passed on Ubuntu in panel CI, including race and browser checks and standalone installer/diagnostic CI.

To install or reapply the installer fixes, run from an interactive SSH terminal:

bash <(curl -fsSL https://raw.githubusercontent.com/WhiteDNS/Soar-Server/main/panel-setup.sh)

WhiteDNS Soar Panel 0.3.0 — Subscriptions and English

WhiteDNS Soar Panel 0.3.0 — Subscriptions and English

Each account now has a private subscription URL and QR code. With WhiteDNS
Android 1.6.8 or later, users import that URL once and refresh it to receive
updated resolver lists, tuning and rotated tunnel keys. Existing direct profiles
continue to work. Responses include quota, usage, expiry and the recommended
12-hour refresh interval.

Subscription credentials are separate from tunnel keys and the private admin
login path. Rotate a subscription URL to revoke its downloads; disable the
account or rotate its tunnel key to revoke previously downloaded access.
Deleted accounts invalidate their subscription. Inactive accounts export no
profile. Use HTTPS for subscription delivery.

The login page and toolbar now switch the full interface between Persian and
English, with RTL/LTR layout, localized dates, menus, messages and field help.
The choice persists in the browser. User-entered names and notes are preserved.
An English installation guide is included in the offline bundle.

Upgrade from Panel updates, or rerun the README installer. Existing accounts,
usage, keys, tuning, TLS settings and private login path are retained. Download a
backup first. New backups preserve subscription URLs; 0.2.0 backups remain
readable, but 0.3.0 backups require 0.3.0 or later for restore. Restoring an older
backup also restores that backup's token state.

See subscription usage and security,
English installation and راهنمای فارسی.
The tunnel engine is Lantern Soar.

WhiteDNS Soar Panel 0.2.0 — Stable

WhiteDNS Soar Panel 0.2.0 — Stable

First stable management-panel release, promoted from beta10. Lantern develops
the Soar engine; WhiteDNS maintains the panel, installer and client integration.

• Separate account links/QRs, durable traffic budgets, expiry, shared speed and
  TCP stream limits; preserve keys and counters across upgrades.
• Persian responsive dashboard, dark/light themes, consistent dropdowns and
  help on question-mark controls.
• In-panel backup, restore and updates with administrator reauthentication;
  domain HTTPS, automatic certificate renewal and private login paths.
• Adaptive profile exports preserve existing explicit tuning. Stable installs
  discover stable updates only; existing betas can graduate to this release.

Installation and upgrade

bash <(curl -fsSL https://raw.githubusercontent.com/WhiteDNS/Soar-Server/main/panel-setup.sh)

The README now points to this stable panel installer. It pins 0.2.0, verifies
archive and internal checksums, and preserves stdin for the guided seven steps.
Supported: Ubuntu 22.04/24.04/26.04 or Debian 12/13 on amd64, systemd, root/sudo.
No Go, Node, Docker or separate database is required on the VPS.
The legacy setup.sh remains the standalone server installer without a panel.

Back up first. Beta8 and later can update from the panel; older installations
should rerun the panel installer once to install maintenance support. Accounts,
keys, usage, saved tuning and HTTPS/private-path settings are retained.
Standalone-to-panel migration requires explicit confirmation and new account
links; shared-root profiles do not migrate automatically.

The panel is stable; the Android transport patch remains a prerelease. For the
browser reliability fix use
WhiteDNS 1.6.7-beta2 or newer,
save adaptive tuning and reimport the same account's link. A server upgrade
cannot replace an installed native client engine.

Checks and limits

Release gates cover Go tests, race detection, vet, installer/bootstrap checks,
offline bundle verification and account/settings/maintenance browser workflows.
The server wire format is unchanged.

Stable panel status does not certify Iranian carrier reachability, all websites,
physical Android Full VPN or production-scale load. Amazon automated responses
included anti-bot/intermediary pages. One earlier final-candidate run stalled
with unresponsive DNS paths and remains unexplained; later cache-free runs
succeeded. See the root-cause report
and Persian installation guide.

WhiteDNS Soar Panel 0.2.0-beta9

WhiteDNS Soar Panel 0.2.0-beta9

This server-side release polishes every dropdown and makes field help unobtrusive. Lantern
remains the author of the Soar engine; existing WhiteDNS profiles and apps keep
their current transport behavior.

• All selection fields now use a shared Persian listbox with consistent fonts,
  spacing, selected checkmarks, dark/light themes and mobile sizing. Keyboard
  navigation, Escape cancellation and outside-click dismissal are supported.

• Field explanations open only from the question-mark button: hover, keyboard
  focus or touch. Hovering or editing an input no longer opens a popup.

• Existing restore, update and secure-access features are retained:

• Restore a panel .db directly in Backup & Restore. Uploaded files are size-limited,
  checked for database integrity, account/key consistency and matching tunnel zone,
  then previewed before confirmation. Current administrator credentials, access
  settings and certificates are preserved. Old backups restore usage to their
  saved point in time. The service stops briefly during the actual replacement.

• Check official WhiteDNS panel releases and install a newer compatible amd64
  release from the panel. Downloads finish before stopping the current service.
  SHA-256 and the GitHub asset digest, when present, are checked. Failed activation
  restores the previous database and executables. Checksums provide integrity
  relative to the official release; they are not an independent code signature.

• A separate root maintenance service exposes only a group-restricted local Unix
  socket. The web panel still runs as the soar-panel user. Requests cannot select
  shell commands, service names, download hosts or installation destinations.
  Private before-operation copies are retained for the five most recent jobs.

• Configure a domain and automatic Let's Encrypt HTTPS from the panel or the
  English terminal wizard (sudo soar-panel-security). A direct A/AAAA record and
  reachable TCP/80 and TCP/443 are required. An existing web server on these ports
  requires a separately configured reverse proxy. Certificate failure preserves
  the existing address. Certificates renew automatically while the service runs.

• Generate a 256-bit random login path. New installations receive one by default;
  existing installations keep their address until they explicitly apply a new one.
  Preview and save the new address before applying it. Old URLs and unprefixed
  assets/API paths return 404. With native HTTPS enabled, public plaintext panel
  access is rejected. Cookies remain HttpOnly/SameSite Strict and are scoped to
  the private path; native HTTPS makes them Secure. A hidden URL supplements
  password authentication and HTTPS rather than replacing them.

Restore, updates and access changes require the current admin password. Service
restarts invalidate browser sessions; sign in again with the same password to
see the last maintenance result. Backup files contain private account keys.

Validation includes restore/rollback and update failure tests, corrupt backup and
key mismatch rejection, authentication/CSRF/password checks, session-bound restore
and access previews, version ordering, safe archive extraction, private-path asset
routing and certificate-failure preservation. Real browser checks retain existing
account/clipboard/settings coverage and add the maintenance views at mobile widths.

The visual system remains the original WhiteDNS implementation inspired by the
supplied Sanaei/3x-ui screenshots. No 3x-ui code or assets are included. This release
does not qualify Iranian access-network behavior or production load capacity.

Install or upgrade the explicit panel beta in an interactive SSH terminal:

bash <(curl -fsSL https://raw.githubusercontent.com/WhiteDNS/Soar-Server/panel-v0.2.0-beta9/panel-setup.sh)

Persian installation, secure access and recovery guide

Certificate automation: Go autocert
and Let's Encrypt challenges.

WhiteDNS Soar Panel 0.2.0-beta8

WhiteDNS Soar Panel 0.2.0-beta8

This server-side release adds restore, updates and secure panel access. Lantern
remains the author of the Soar engine; existing WhiteDNS profiles and apps keep
their current transport behavior.

• Restore a panel .db directly in Backup & Restore. Uploaded files are size-limited,
  checked for database integrity, account/key consistency and matching tunnel zone,
  then previewed before confirmation. Current administrator credentials, access
  settings and certificates are preserved. Old backups restore usage to their
  saved point in time. The service stops briefly during the actual replacement.
• Check official WhiteDNS panel releases and install a newer compatible amd64
  release from the panel. Downloads finish before stopping the current service.
  SHA-256 and the GitHub asset digest, when present, are checked. Failed activation
  restores the previous database and executables. Checksums provide integrity
  relative to the official release; they are not an independent code signature.
• A separate root maintenance service exposes only a group-restricted local Unix
  socket. The web panel still runs as the soar-panel user. Requests cannot select
  shell commands, service names, download hosts or installation destinations.
  Private before-operation copies are retained for the five most recent jobs.
• Configure a domain and automatic Let's Encrypt HTTPS from the panel or the
  English terminal wizard (sudo soar-panel-security). A direct A/AAAA record and
  reachable TCP/80 and TCP/443 are required. An existing web server on these ports
  requires a separately configured reverse proxy. Certificate failure preserves
  the existing address. Certificates renew automatically while the service runs.
• Generate a 256-bit random login path. New installations receive one by default;
  existing installations keep their address until they explicitly apply a new one.
  Preview and save the new address before applying it. Old URLs and unprefixed
  assets/API paths return 404. With native HTTPS enabled, public plaintext panel
  access is rejected. Cookies remain HttpOnly/SameSite Strict and are scoped to
  the private path; native HTTPS makes them Secure. A hidden URL supplements
  password authentication and HTTPS rather than replacing them.

Restore, updates and access changes require the current admin password. Service
restarts invalidate browser sessions; sign in again with the same password to
see the last maintenance result. Backup files contain private account keys.

Validation includes restore/rollback and update failure tests, corrupt backup and
key mismatch rejection, authentication/CSRF/password checks, session-bound restore
and access previews, version ordering, safe archive extraction, private-path asset
routing and certificate-failure preservation. Real browser checks retain existing
account/clipboard/settings coverage and add the maintenance views at mobile widths.

The visual system remains the original WhiteDNS implementation inspired by the
supplied Sanaei/3x-ui screenshots. No 3x-ui code or assets are included. This release
does not qualify Iranian access-network behavior or production load capacity.

Install or upgrade the explicit panel beta in an interactive SSH terminal:

bash <(curl -fsSL https://raw.githubusercontent.com/WhiteDNS/Soar-Server/panel-v0.2.0-beta8/panel-setup.sh)

Persian installation, secure access and recovery guide

Certificate automation: Go autocert
and Let's Encrypt challenges.

WhiteDNS Soar Panel 0.2.0-beta7

WhiteDNS Soar Panel 0.2.0-beta7

An opt-in server-side management panel for Lantern Soar. The familiar sidebar,
dashboard and account editor are inspired by Sanaei/3x-ui; the implementation is
original. Lantern remains the author of the Soar tunneling engine.

This release replaces the account table's native More select with a compact action
menu inspired by the supplied 3x-ui reference. It uses the panel's bundled Persian
font, matching surfaces, consistent line icons and a separate red delete action.
The popover escapes the table's scroll container and flips within the viewport.
Keyboard arrows, Home/End, Escape, outside-click dismissal and focus restoration
are supported. Background polling keeps an open menu stable. Existing operations
and their confirmation dialogs are preserved; no account or transport changes.
Browser checks cover menu placement, typography, keyboard navigation, cancellation,
responsive layouts and the existing account and clipboard workflows.

The profile-copy fix from beta6 is retained. The Copy button
writes the entire link to the clipboard using the browser's supported method,
including a fallback when the secure clipboard API is unavailable or denied.
Browsers that block both methods show an honest error with manual-copy/download
instructions instead of claiming success.

Copy feedback appears inside the active dialog, above the native modal backdrop,
with readable success/error colors in both themes. Closing the dialog clears it.
Browser checks read the actual clipboard and compare the full link on HTTPS-capable
local and genuinely insecure HTTP origins, including denied-API fallback, blocked
commands, mobile sizing and contrast. Accounts, links and settings are unchanged.

The panel retains the redesign introduced in beta5:
compact charcoal surfaces, a consistent blue action color, locally bundled
Vazirmatn typography, aligned controls and a responsive right navigation rail.
Login, dashboard, accounts, settings, events, backup and dialogs share the same
visual system. A light theme and the existing appearance preference are retained.

The dashboard shows resource readings and real sample history, DNS send/receive
rates and open tunnel streams. Charts start when the page opens, retain up to ten
minutes in memory and clear on server counter reset. Missing metrics remain
unavailable; no historical values are fabricated. DNS rates include DNS overhead
and are distinct from the per-account TCP payload quota counters.

Login has an accessible password visibility control and a theme toggle. Mobile
navigation supports dismissal and keyboard focus. All 20 settings explanations
remain available through hover, focus and touch. The font and icons need no CDN.

Existing accounts, keys, usage, quotas and advanced transport tuning are preserved.
The redesign does not require reimporting a profile or updating the Android app.
The Soar transport implementation is unchanged.

Validation covers real browser account workflows, persistent tuning, bundled-font
loading, login controls, light/dark themes, tooltips and responsive layouts at
320/375/414/768/1440 pixels, plus the existing backend, race and installer checks.
The font's SIL Open Font License ships with the bundle.

• Create independent accounts and export existing WhiteDNS-compatible links/QRs.
• Set combined upload/download quota, expiry, shared speed and concurrent TCP streams.
• Disable access, disconnect streams, reset usage or revoke/replace an account link.
• View real Linux resource statistics, separate traffic counters and management events.
• Download durable backups, export accounts and configure discovery/resolver defaults.
• Persian RTL, mobile layout, light/dark themes; English-only SSH installation steps.

No WhiteDNS update is required. Migrating a standalone server requires new
per-account profile links. The old shared-root profile stops working after migration;
the installer explains this and preserves the previous service/config for rollback.

The installer now offers direct browser access using the server IP and chosen
TCP port, plus a private SSH/HTTPS-proxy option. It displays the actual access URL.
Direct HTTP is an explicit test-server mode and is unencrypted; the CLI otherwise
retains its TLS/private-access checks. Upgrades preserve accounts, links and usage.
Backups contain private account keys. A TCP stream limit is not a device limit;
anyone sharing one profile shares its budget. Payload accounting excludes DNS overhead.

This is a beta, initially Linux amd64. It has automated tunnel, quota, authentication,
race and browser tests, plus a live Ubuntu/systemd deployment check. Real Iranian
access-network validation and production load qualification remain outstanding.

Install the explicit panel beta (in an interactive SSH terminal):

bash <(curl -fsSL https://raw.githubusercontent.com/WhiteDNS/Soar-Server/panel-v0.2.0-beta7/panel-setup.sh)

Persian installation, migration and recovery guide

WhiteDNS Soar Panel 0.2.0-beta6

WhiteDNS Soar Panel 0.2.0-beta6

An opt-in server-side management panel for Lantern Soar. The familiar sidebar,
dashboard and account editor are inspired by Sanaei/3x-ui; the implementation is
original. Lantern remains the author of the Soar tunneling engine.

This release fixes profile link copying on public HTTP addresses. The Copy button
writes the entire link to the clipboard using the browser's supported method,
including a fallback when the secure clipboard API is unavailable or denied.
Browsers that block both methods show an honest error with manual-copy/download
instructions instead of claiming success.

Copy feedback appears inside the active dialog, above the native modal backdrop,
with readable success/error colors in both themes. Closing the dialog clears it.
Browser checks read the actual clipboard and compare the full link on HTTPS-capable
local and genuinely insecure HTTP origins, including denied-API fallback, blocked
commands, mobile sizing and contrast. Accounts, links and settings are unchanged.

The panel retains the redesign introduced in beta5:
compact charcoal surfaces, a consistent blue action color, locally bundled
Vazirmatn typography, aligned controls and a responsive right navigation rail.
Login, dashboard, accounts, settings, events, backup and dialogs share the same
visual system. A light theme and the existing appearance preference are retained.

The dashboard shows resource readings and real sample history, DNS send/receive
rates and open tunnel streams. Charts start when the page opens, retain up to ten
minutes in memory and clear on server counter reset. Missing metrics remain
unavailable; no historical values are fabricated. DNS rates include DNS overhead
and are distinct from the per-account TCP payload quota counters.

Login has an accessible password visibility control and a theme toggle. Mobile
navigation supports dismissal and keyboard focus. All 20 settings explanations
remain available through hover, focus and touch. The font and icons need no CDN.

Existing accounts, keys, usage, quotas and advanced transport tuning are preserved.
The redesign does not require reimporting a profile or updating the Android app.
The Soar transport implementation is unchanged.

Validation covers real browser account workflows, persistent tuning, bundled-font
loading, login controls, light/dark themes, tooltips and responsive layouts at
320/375/414/768/1440 pixels, plus the existing backend, race and installer checks.
The font's SIL Open Font License ships with the bundle.

• Create independent accounts and export existing WhiteDNS-compatible links/QRs.
• Set combined upload/download quota, expiry, shared speed and concurrent TCP streams.
• Disable access, disconnect streams, reset usage or revoke/replace an account link.
• View real Linux resource statistics, separate traffic counters and management events.
• Download durable backups, export accounts and configure discovery/resolver defaults.
• Persian RTL, mobile layout, light/dark themes; English-only SSH installation steps.

No WhiteDNS update is required. Migrating a standalone server requires new
per-account profile links. The old shared-root profile stops working after migration;
the installer explains this and preserves the previous service/config for rollback.

The installer now offers direct browser access using the server IP and chosen
TCP port, plus a private SSH/HTTPS-proxy option. It displays the actual access URL.
Direct HTTP is an explicit test-server mode and is unencrypted; the CLI otherwise
retains its TLS/private-access checks. Upgrades preserve accounts, links and usage.
Backups contain private account keys. A TCP stream limit is not a device limit;
anyone sharing one profile shares its budget. Payload accounting excludes DNS overhead.

This is a beta, initially Linux amd64. It has automated tunnel, quota, authentication,
race and browser tests, plus a live Ubuntu/systemd deployment check. Real Iranian
access-network validation and production load qualification remain outstanding.

Install the explicit panel beta (in an interactive SSH terminal):

bash <(curl -fsSL https://raw.githubusercontent.com/WhiteDNS/Soar-Server/panel-v0.2.0-beta6/panel-setup.sh)

Persian installation, migration and recovery guide