[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1zkbexe3fknnj":3},{"code":4,"message":5,"data":6,"timestamp":26},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":22,"homepage":23,"updated_at":24,"history":25},"WhiteDNS\u002FSoar-Server",23,"Guided Soar server installer for Ubuntu 24.04 amd64, with Persian documentation and WhiteDNS IR\u002FGLOBAL profiles","Go",119,16,15,7,[],"Turns a fresh Ubuntu or Debian VPS into a managed DNS-tunnel server with a browser panel, accounts and subscriptions.","If you already run a Lantern Soar-style DNS tunnel and want per-user accounts, quotas and a web panel instead of hand-editing config, this installer is worth a look — with the caveats below.\n\n## The problem\nSetting up a DNS tunnel server normally means provisioning a VPS, pointing a domain at it, opening port 53, then editing config files and creating user keys by hand. Each new user becomes another manual edit, and giving someone a link or QR code is your own problem. Here, a guided installer takes a fresh Ubuntu or Debian machine through seven steps, creates the panel, and then account creation, links, QR codes and subscriptions happen in a browser dashboard. The result is a working panel address with a random path and per-account connection details.\n\n## What's different\nThe distinguishing choice is the guided installer rather than a stack of manual steps. One command downloads the stable release bundle for the server's architecture and verifies its checksum before changing the service; if that lookup or check fails, installation stops rather than replacing the old version. During install it checks A\u002FNS records first, then runs an HTTPS test from inside the tunnel, and offers to retry, roll back or keep an explicitly \"unverified\" install, which exits non-zero. It also handles UFW rules for DNS and the management port after confirmation.\n\nThe panel then wraps three engines — Soar, Cotten and MasterDNS — under one account model, so a single account can expose several connection methods while sharing volume, expiry and speed limits. That is convenient for distributing one subscription to multiple clients, but the README is explicit that the shared link carries the same account identity, so it is not per-device isolation. Anti-abuse controls (connection-rate limits, destination scanning detection, upload ceilings and temporary quarantine) are shared across engines and enabled by default; these are separate from per-account traffic caps. The docs also note browser-interface reliability issues recorded in a dated report, so the panel is not presented as fully battle-tested.\n\n## Who should try it\nA good fit is someone administering a small set of users on their own Ubuntu 22.04\u002F24.04\u002F26.04 or Debian 12\u002F13 server, who wants accounts, quotas and shareable subscription links without building that management layer. The fact that the terminal installer is English\u002FASCII while the panel and guides are Persian-first matters: if you need Persian documentation and a Persian UI, this is unusually complete, and an English installation guide plus subscription docs also exist.\n\nA poor fit is anyone expecting general-purpose proxy coverage: the README scopes the release to TCP 80\u002F443 destinations and says UDP\u002FQUIC, games and calls are not covered. Nor is it for someone who wants a fully verified production rollout today — physical-device, Iran-network and large production load testing are described as not yet complete.\n\n## Requirements and limitations\nYou need root or sudo with systemd on a supported Ubuntu\u002FDebian release and architecture (amd64\u002Fx86_64 or arm64\u002Faarch64); Go, Docker, Node and a separate database are not needed on the server. You must control a domain and its DNS records and have UDP\u002F53 and TCP\u002F53 reachable, with provider firewall and NAT configured outside the installer; UFW handling is only part of the path. The panel URL includes a random path that you must save, and account changes require refreshing the subscription or re-importing the direct link in the WhiteDNS app (1.6.8 or newer for full subscriptions).\n\nOngoing upkeep has two traps. Updating the binary alone does not rerun DNS checks or installation tests; the installer must be rerun for that. Versions older than beta8 need one installer run to get the maintenance service, and the docs advise backing up before upgrades. The older panel-less `setup.sh` path is still documented but is managed via `sudo soar-manager`, and migrating from its shared profile to panel accounts requires confirmation and fresh account links.\n\n## HotRepo's take\nHotRepo first tracked this repository at 7 days old (created 2026-10-17) and recorded 119 total stars at #23 on the NEW-REPOSITORY board on 2026-10-25 — a snapshot of a young project, not a daily growth figure or an overall Trending rank. With only two recorded dates and no comparable daily-board history, persistence cannot yet be judged. Before committing, verify the supported-release matrix and the random-path login behaviour in the [installation guide](https:\u002F\u002Fgithub.com\u002FWhiteDNS\u002FSoar-Server\u002Fblob\u002Fmain\u002Fdocs\u002FPANEL.en.md) and the noted [browser-interface reliability report](https:\u002F\u002Fgithub.com\u002FWhiteDNS\u002FSoar-Server\u002Fblob\u002Fmain\u002Fdocs\u002FSOAR-WEB-RELIABILITY-2026-10-18.fa.md).",{"slug":19,"name":20},"devops","DevOps & Self-hosting",[],"Apache-2.0",null,"2026-10-25T03:18:27Z",[],1792906246]