Angie Panel Why Features Install GitHub

Reverse proxy management
without the Docker stack

A web UI for Angie — like nginx-proxy-manager, but a plain systemd service, with certificates issued by Angie itself instead of certbot.

Running in production MIT licensed arm64 · amd64 ~10–20 MB RAM No Docker
Install it View source
Proxy host list with live uptime bars per host

Why not nginx-proxy-manager?

Same job, different trade-offs. This one is built for a box that just runs — an SBC in a cupboard, a small VPS — where a container stack is overhead you feel.

Certificates

Angie issues them, not certbot

http-01, tls-alpn-01 and dns-01 including wildcards, handled by Angie's built-in ACME module. No certbot, no pip, no renewal cron — and nothing to keep alive just to hold a certificate.

Applying changes

The pipeline tells you the truth

You see a diff before anything is written. The staged config is validated with angie -t, written atomically, and rolled back from a snapshot if the reload fails. Files edited by hand on disk are detected and shown.

Privileges

The panel never runs as root

Config is generated by an unprivileged user. A small auditable helper — invoked through a systemd oneshot unit behind polkit — is the only thing that writes to /etc.

Footprint

One binary, one service

A single static musl binary in a .deb, with the UI embedded. No runtime dependencies, no container, no database server — state lives in one SQLite file.

What it does

Hosts

Proxy, redirection and 404 hosts, TCP/UDP streams, SNI routers. Per host: websockets, HTTP/2 and HTTP/3, HSTS, custom locations, upstreams with load balancing, rate limits, headers, gzip, error pages, maintenance mode, mTLS, forward auth.

Certificates

Issued and renewed by Angie. DNS-01 talks to provider APIs through a vendored acme.sh; the hook waits for the TXT record to reach every authoritative nameserver before letting the CA check.

Availability

Opt-in TCP and HTTP(S) checks per host, with history and an uptime bar in the list. HTTP checks go over loopback with the domain as SNI and verify the certificate.

Security

Access lists with basic auth and IP rules, an IP blocklist, GeoIP country policy, an audit log, and users with roles.

Operations

A dashboard fed by Angie's own status API, apply history, drift detection, and config export/import as JSON. The apctl CLI drives the same API the browser does — so scripted changes get the same validation, rollback and audit trail — and ships for Linux, macOS and Windows on arm64 and x86_64.

Both languages

The interface ships in English and Russian, with a light and a dark theme that follow the system by default.

A look around

Dashboard with Angie metrics and per-host traffic
Dashboard — live Angie metrics, certificate state, per-host traffic.
Certificate list showing challenge type and status
Certificates — issued by Angie: http-01, dns-01, wildcards.
Host editor dialog with thirteen configuration sections
Host editor — thirteen sections, from SSL to rate limits.
Settings page with defaults for the whole install
Settings — defaults that every host inherits.

Install

Debian or Ubuntu on arm64 or amd64, with Angie already installed. The installer adds the service, the systemd units and the polkit rule.

# download, read it, then run it curl -fsSL https://github.com/maxname/angie-panel/releases/latest/download/install.sh -o install.sh less install.sh sudo bash install.sh

There is no default password. Take the one-time setup token and create the first administrator at http://<host>:8080/setup:

sudo cat /var/lib/angie-panel/setup-token

The command-line tool

On the panel host, apctl came with the package — no token needed, it reads the local one. To drive the panel from your own machine, grab the standalone binary for your platform (Linux, macOS and Windows, arm64 and x86_64) and point it at the panel:

# on the server sudo apctl status # on macOS or Linux elsewhere brew install maxname/tap/apctl # then point it at the panel — create a token on the API tokens page first export ANGIE_PANEL_TOKEN=ap_… apctl --url https://panel.example.com status

Downloads for every platform, verification, and the full command list are in the CLI guide.

Before you expose it. Whoever controls Angie's configuration controls the host — Angie's master runs as root. Treat access to this panel as root access: bind it to your LAN, or publish it behind the proxy it manages with an access list in front. See the security policy.
Latest release Installation guide