{"id":1143,"date":"2026-11-22T03:00:00","date_gmt":"2026-11-22T03:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1143"},"modified":"2026-11-22T03:00:00","modified_gmt":"2026-11-22T03:00:00","slug":"install-firezone-ui-wireguard-vpn-debian-12","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/22\/install-firezone-ui-wireguard-vpn-debian-12\/","title":{"rendered":"Install Firezone UI for WireGuard on Debian 12"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">To install Firezone UI for WireGuard VPN on Debian 12 today, deploy a Firezone Gateway on your VPS and manage it from the Firezone Admin Portal. The current setup takes about 10 minutes and gives approved users access to private servers, apps, or subnets through Firezone\u2019s WireGuard-based client.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The old all-in-one Firezone 0.7 web interface is end-of-life, so this guide uses the supported architecture: Firezone hosts the control plane while your Debian server runs the Gateway.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Debian 12 (Bookworm) on a 64-bit VPS with a public or otherwise reachable network connection.<\/li>\n\n\n<li>A root shell or a sudo-enabled user connected over SSH.<\/li>\n\n\n<li>At least 1 vCPU and 1 GB RAM for a small Gateway; choose more CPU, memory, and bandwidth as your client count grows.<\/li>\n\n\n<li>The server must be able to reach the internet and the private resource you want to publish through Firezone.<\/li>\n\n\n<li>A free or paid Firezone account and an end-user device for testing. The current deployment does not require a domain name or a local TLS certificate.<\/li>\n\n\n<li>A fresh <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> with Debian 12 is suitable for this Gateway.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Update Debian and install prerequisites<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Updating the base system and installing the packet-filtering tools gives the Gateway the commands it expects on Debian 12.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update\nsudo apt full-upgrade -y\nsudo apt install -y ca-certificates gnupg iptables wget<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Confirm the server is Debian 12 and that both IPv4 and IPv6 firewall commands exist:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>. \/etc\/os-release &amp;&amp; printf '%s\\n' \"$PRETTY_NAME\"\niptables --version\nip6tables --version<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output includes <code>Debian GNU\/Linux 12<\/code> and an <code>iptables v1.x<\/code> version for each command.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Create a Firezone Site and Gateway token<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The portal creates the Gateway identity and gives this one server a single-owner token; the token is not a replacement for your Debian login password.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Open the <a href=\"https:\/\/app.firezone.dev\/\" target=\"_blank\" rel=\"noopener\">Firezone Admin Portal<\/a> and create an account or sign in.<\/li>\n\n\n<li>Open <strong>Sites \u2192 Add Site<\/strong>, give the site a name such as <code>Debian-12-VPS<\/code>, and save it.<\/li>\n\n\n<li>On the new Site Details page, select <strong>Deploy a Gateway<\/strong>.<\/li>\n\n\n<li>Select the Debian\/Ubuntu installation method and copy the one-time Gateway token into a password manager.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Do not paste the token into a shared ticket, commit it to a repository, or put it directly in a shell command. Each new Gateway should get its own token.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Add the official Firezone APT repository<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Firezone repository supplies the current Gateway package and its systemd service, so you can update it with Debian\u2019s normal package tools.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mkdir --parents \/etc\/apt\/keyrings\nwget -qO- https:\/\/artifacts.firezone.dev\/apt\/key.gpg | sudo gpg --dearmor --yes -o \/etc\/apt\/keyrings\/firezone.gpg\necho \"deb [signed-by=\/etc\/apt\/keyrings\/firezone.gpg] https:\/\/artifacts.firezone.dev\/apt\/ stable main\" | sudo tee \/etc\/apt\/sources.list.d\/firezone.list &gt; \/dev\/null\nsudo apt update\nsudo apt install -y firezone-gateway<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The package installation should finish without an <code>Unable to locate package<\/code> error. The repository and package instructions are also documented in the <a href=\"https:\/\/www.firezone.dev\/kb\/deploy\/debian\" target=\"_blank\" rel=\"noopener\">Firezone Debian deployment guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Authenticate and start the Gateway<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Authentication registers this VPS with the Site you created, then systemd keeps the Gateway running after disconnects and reboots.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the interactive command and paste the token when prompted:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firezone-gateway authenticate<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Now check the service:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-enabled firezone-gateway\nsudo systemctl is-active firezone-gateway\nsudo systemctl status firezone-gateway --no-pager<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output includes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>enabled\nactive\nActive: active (running)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Return to <strong>Firezone Admin Portal \u2192 Sites \u2192 Debian-12-VPS<\/strong>. The Gateway should appear as online. If it remains offline, keep the terminal open and inspect the service log in the Troubleshooting section.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Keep the VPS firewall narrow<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The current architecture does not expose a Firezone web dashboard on the VPS, so you do not need to open ports 80 or 443 or install a local certificate. Keep inbound access limited to SSH and allow outbound connections to the Firezone control plane and your resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If UFW is already your firewall, preserve your SSH session before enabling or changing it, then use:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ufw allow OpenSSH\nsudo ufw default deny incoming\nsudo ufw default allow outgoing\nsudo ufw --force enable\nsudo ufw status verbose<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output shows the firewall active, OpenSSH allowed, incoming traffic denied by default, and outgoing traffic allowed. Do not add broad inbound rules just because older self-hosted Firezone instructions used HTTPS on the server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Add a resource, policy, and client<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A Gateway being online only establishes the tunnel; Firezone\u2019s default-deny policy still requires you to name a resource and authorize a user group.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>In <strong>Site Details \u2192 Add Resource<\/strong>, enter a name such as <code>Private-Web<\/code> and the destination address. Use an IP address, FQDN, or CIDR range such as <code>10.20.0.15<\/code>, <code>db.internal.example<\/code>, or <code>10.20.0.0\/24<\/code>.<\/li>\n\n\n<li>Open <strong>Policies \u2192 Add Policy<\/strong>, select the resource, and grant access to the intended group. Save the policy.<\/li>\n\n\n<li>Open the <a href=\"https:\/\/www.firezone.dev\/kb\/install\" target=\"_blank\" rel=\"noopener\">Firezone client download page<\/a>, install the client on a test device, and sign in with your Firezone account slug.<\/li>\n\n\n<li>In the client, select the resource you authorized and connect.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The Gateway must be able to route to the resource from the VPS. A policy cannot make an unreachable private network reachable by itself.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Gateway and private access<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">First verify the local service and its recent logs:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active firezone-gateway\nsudo journalctl -u firezone-gateway -n 30 --no-pager<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output is <code>active<\/code> followed by recent service entries without repeated authentication or connection failures. The Admin Portal should show the Gateway as online.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Next, test the resource from the Firezone client. For an HTTP resource, substitute its address and port:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl --connect-timeout 5 http:\/\/RESOURCE_IP:PORT\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>RESOURCE_IP<\/code> and <code>PORT<\/code> with a service that is intentionally allowed by your policy. A response from that service proves the client, policy, Gateway, and resource path are working together. For SSH or RDP, use the same private address in the normal client after the Firezone tunnel reports connected.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><code>Unable to locate package firezone-gateway<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">APT has not loaded the Firezone repository, or the repository file\/key was created incorrectly. Re-run the repository commands in Step 3, then run <code>sudo apt update<\/code> and confirm that <code>sudo apt install firezone-gateway<\/code> now finds a candidate package.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>Authentication failed<\/code> or the token is already claimed<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Current Gateway tokens are single-owner tokens. In <strong>Sites \u2192 YOUR_SITE \u2192 Gateways<\/strong>, remove or rotate the stale Gateway, choose <strong>Deploy a Gateway<\/strong> again, and authenticate this VPS with the newly generated token. Never reuse a token on two active servers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The Gateway stays offline<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check <code>sudo journalctl -u firezone-gateway -n 50 --no-pager<\/code> for DNS, TLS, or network errors. Confirm the VPS has working DNS and outbound internet access, and check any VPS provider firewall or corporate egress filter; the current Gateway does not need an inbound dashboard port.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The client connects but cannot reach the resource<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is usually a policy or routing problem. Confirm the resource address is correct, the user belongs to the group selected by the policy, and the Debian server can reach the destination directly with a suitable test such as <code>curl<\/code> or <code>nc<\/code>; also check that the resource\u2019s own firewall permits traffic from the Gateway path.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening and maintenance<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Treat the Gateway token like a password. Rotate it in the Firezone portal if it was exposed, then restart or re-authenticate the service with the replacement token.<\/li>\n\n\n<li>Restrict SSH to trusted source addresses at the VPS provider firewall when possible, and use SSH keys instead of password authentication.<\/li>\n\n\n<li>Apply Gateway updates through APT and review the service after each upgrade:<\/li>\n\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>  sudo apt update\n  sudo apt install --only-upgrade firezone-gateway\n  sudo systemctl is-active firezone-gateway<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>For production availability, place Gateways in separate hosts and create one token per Gateway rather than cloning this server\u2019s credentials.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I open the Firezone dashboard at my VPS IP address?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not with the current Firezone architecture. The admin interface is hosted in the Firezone Admin Portal, while the Debian server runs only the Gateway data-plane service.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need Docker to install Firezone on Debian 12?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The native APT method installs <code>firezone-gateway<\/code> as a systemd service and is the shortest route on Debian. Firezone also documents a Docker Gateway deployment if you already operate Docker on the host.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does this create a traditional <code>wg0<\/code> configuration file?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The current Gateway manages the WireGuard-based tunnel and its routing through the Firezone service. You configure Sites, resources, groups, and policies in the portal instead of distributing hand-written <code>wg-quick<\/code> peer files.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is a domain required for the Debian 12 Gateway?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. A domain and local certificate were needed by older self-hosted web UI instructions, but this Gateway connects to the hosted control plane and does not publish a local HTTPS interface.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Deploy Firezone faster\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Debian 12 VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Deploy Firezone faster<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Start with a Debian 12 VPS ready for secure remote access.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-vps\" aria-label=\"View VPS plans\">View VPS plans<\/a>\n<\/aside>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I open the Firezone dashboard at my VPS IP address?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not with the current Firezone architecture. The admin interface is hosted in the Firezone Admin Portal, while the Debian server runs only the Gateway data-plane service.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need Docker to install Firezone on Debian 12?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The native APT method installs `firezone-gateway` as a systemd service and is the shortest route on Debian. Firezone also documents a Docker Gateway deployment if you already operate Docker on the host.\"}}, {\"@type\": \"Question\", \"name\": \"Does this create a traditional `wg0` configuration file?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The current Gateway manages the WireGuard-based tunnel and its routing through the Firezone service. You configure Sites, resources, groups, and policies in the portal instead of distributing hand-written `wg-quick` peer files.\"}}, {\"@type\": \"Question\", \"name\": \"Is a domain required for the Debian 12 Gateway?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. A domain and local certificate were needed by older self-hosted web UI instructions, but this Gateway connects to the hosted control plane and does not publish a local HTTPS interface.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Firezone UI for WireGuard VPN on Debian 12 with the current Gateway method, secure SSH setup, firewall guidance, and client verification.","protected":false},"author":1,"featured_media":1144,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[5,9],"tags":[97,146,148,147],"class_list":["post-1143","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-debian-12","tag-firezone","tag-vpn","tag-wireguard","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/comments?post=1143"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1143\/revisions"}],"predecessor-version":[{"id":4153,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1143\/revisions\/4153"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1144"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}