Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host Zoraxy
updated Sep 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A general-purpose reverse proxy managed entirely from a web UI, built for homelabs: proxy rules with load balancing and basic auth, redirection rules, ACME certificates with auto-renew and DNS challenges, TCP/UDP stream proxying, country and IP allow/deny lists, plus an uptime monitor, web SSH terminal and network utilities in the same AGPL-3.0 Go binary. The admin UI listens on port 8000 and asks you to create the single admin account on first visit.
Pick Zoraxy when you want Nginx Proxy Manager's point-and-click model with more in the box: load balancing, country-level allow/deny lists, an uptime monitor and a web SSH terminal alongside the proxy rules, ACME certificates and TCP/UDP streams both have — all one AGPL-3.0 Go binary with its admin UI on port 8000. It is built with homelabs in mind; on a single VPS with a few apps, Nginx Proxy Manager or Caddy is the simpler choice.
What you need
Any VPS with at least 256 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Zoraxy — a single Go binary; the project's Getting Started guide steers anyone not fluent in Docker networking to it over the image# pick the newest tag without an -rc suffix from the Releases page — "latest" can point at a release candidatesudo mkdir -p /opt/zoraxy && cd /opt/zoraxysudo wget -O zoraxy_linux_amd64 https://github.com/tobychui/zoraxy/releases/download/v3.3.4/zoraxy_linux_amd64sudo chmod +x zoraxy_linux_amd64# run it as a service — the unit from the project's FAQ (root, because Zoraxy binds ports 80/443)sudo tee /etc/systemd/system/zoraxy.service >/dev/null <<'EOF'[Unit]Description=Zoraxy Reverse Proxy ServerAfter=network-online.targetWants=network-online.target[Service]Type=simpleUser=rootGroup=rootWorkingDirectory=/opt/zoraxyExecStart=/opt/zoraxy/zoraxy_linux_amd64 -port=:8000[Install]WantedBy=multi-user.targetEOFsudo systemctl daemon-reload && sudo systemctl enable --now zoraxy# open http://SERVER_IP:8000, create the admin account, add proxy rules, then request certificates from the ACME tool# native binary, not a container — so no idle-RAM reading here (our harness measures Docker only)# the repo's docker/ folder documents zoraxydocker/zoraxy if you prefer a container
Zoraxy is actively developed and its docs are candid; three points matter before you install:
non-negotiableThe project's Getting Started guide says that if you are "not experienced with networking in a dockerized environment, DO NOT use the docker version": many features rely on protocol sniffing and "usually require direct access to the networking interface and the original (unmodified) request". That is why our snippet runs the binary. The Docker image (zoraxydocker/zoraxy, documented in the repo's docker/ folder) exists, publishes 80, 443, 443/udp and 8000, and mounts the Docker socket for extra features.
non-negotiableCertificates are not automatic per host the way Caddy's are: you set an ACME email, enable auto-renew, request the certificate for your domains in the ACME tool, then enable TLS on port 443 and the HTTP→HTTPS redirect in the status tab.
non-negotiableThe admin UI on port 8000 has a single admin account created on first visit, and nothing else protects it. Our advice is to keep 8000 off the public firewall. Anything permanent should run under systemd; the project wiki's FAQ has a service file.
non-negotiableThe fast GeoIP option (-fastgeoip / FASTGEOIP) "requires 1GB extra memory" per the docs and is not recommended for low-end devices; leave it off on a small VPS. The 256 MB floor is our estimate with it off; upstream publishes no RAM figure.