{"id":1145,"date":"2026-11-22T09:00:00","date_gmt":"2026-11-22T09:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1145"},"modified":"2026-11-22T09:00:00","modified_gmt":"2026-11-22T09:00:00","slug":"install-firezone-ui-wireguard-vpn-debian-13","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/22\/install-firezone-ui-wireguard-vpn-debian-13\/","title":{"rendered":"Install Firezone UI for WireGuard VPN on Debian 13"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">To install Firezone UI for WireGuard VPN on Debian 13, you will deploy the current Firezone Gateway and manage it from the hosted Admin Portal. In about 10 minutes, your VPS can connect approved users to a private server, application, or subnet through Firezone\u2019s WireGuard-based client.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The current product is not a local web dashboard running on ports 80 and 443. Debian runs the Gateway data plane, while the Firezone portal handles sites, users, resources, and access policies.<\/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 13 (Trixie), 64-bit, with a current kernel and a reachable internet connection.<\/li>\n\n\n<li>A root shell or a sudo-enabled account connected over SSH.<\/li>\n\n\n<li>At least 1 vCPU and 1 GB of RAM for a small Gateway; use more CPU, memory, and bandwidth as your traffic and client count increase.<\/li>\n\n\n<li>Network access from the VPS to the private resource you will publish through Firezone.<\/li>\n\n\n<li>A Firezone account, a browser for the Admin Portal, and a separate device on which to install the Firezone Client.<\/li>\n\n\n<li>No domain name or local TLS certificate is required for this Gateway deployment.<\/li>\n\n\n<li>A fresh <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> running Debian 13.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Update Debian and check the host<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Updating the base system and confirming the packet-filtering commands prevents an incomplete Gateway installation later.<\/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\">Check the release and the required firewall commands:<\/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 identifies <code>Debian GNU\/Linux 13<\/code> and prints an <code>iptables v1.x<\/code> version for both commands. If you are already logged in as root, remove <code>sudo<\/code> from the commands in this guide.<\/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 Site groups your Gateway with the resources it can reach, and its single-owner token registers this particular VPS.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Sign in to the <a href=\"https:\/\/app.firezone.dev\/\" target=\"_blank\" rel=\"noopener\">Firezone Admin Portal<\/a>.<\/li>\n\n\n<li>Open <strong>Sites<\/strong> and select <strong>Add Site<\/strong>. Name it something recognizable, such as <code>Debian13-VPS<\/code>, then save it.<\/li>\n\n\n<li>From the new Site\u2019s details page, choose <strong>Deploy a Gateway<\/strong>.<\/li>\n\n\n<li>Keep the Debian installation instructions open and copy the token into a password manager.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The token is a credential, not a normal Debian password. Generate a separate token for every Gateway, and never put it in a public repository, ticket, screenshot, or shared shell history.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Install the Firezone Gateway package<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The signed Firezone APT repository provides the Gateway binary and its systemd service without adding Docker or a local web stack.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo install -d -m 0755 \/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\">Confirm that APT sees a candidate from the Firezone repository:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt-cache policy firezone-gateway<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The output should show an installed or candidate version and the <code>artifacts.firezone.dev\/apt<\/code> repository. The <a href=\"https:\/\/www.firezone.dev\/kb\/deploy\/debian\" target=\"_blank\" rel=\"noopener\">official Debian deployment instructions<\/a> use this repository and package name.<\/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 saves the Gateway identity locally and connects the service to the Site you created in the portal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the interactive command:<\/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\">When prompted, paste the one-time token from <strong>Sites \u2192 YOUR_SITE \u2192 Deploy a Gateway<\/strong>. The command should register the VPS and create the <code>firezone-gateway<\/code> systemd service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check that systemd enabled and started it:<\/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 -l<\/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 YOUR_SITE<\/strong>. The Gateway should be listed as online. If it is offline, leave the token alone and use the log checks in Troubleshooting instead of repeatedly authenticating.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Apply a narrow Debian firewall policy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Firezone Gateways normally initiate their connections outbound, so the VPS does not need a public dashboard port; protect the host by allowing SSH and denying unsolicited inbound traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a fresh server that does not already use another firewall, install and enable UFW like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install -y ufw\nsudo 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 reports <code>Status: active<\/code>, allows <code>22\/tcp<\/code> through the <code>OpenSSH<\/code> profile, denies incoming traffic by default, and allows outgoing traffic. Keep your current SSH session open while applying the policy, and add a custom SSH port rule before enabling UFW if your server does not use port 22.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Firezone may need outbound HTTPS on TCP 443 plus STUN\/TURN traffic when direct paths are negotiated. If your provider or organization filters egress, allow the destinations and ports in Firezone\u2019s <a href=\"https:\/\/www.firezone.dev\/kb\/reference\/ports\" target=\"_blank\" rel=\"noopener\">ports and protocols reference<\/a>. Stateful cloud firewalls generally do not need a new inbound Firezone rule.<\/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\">An online Gateway only provides the path; a Resource and Policy decide what an authenticated user can actually reach.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>In <strong>Firezone Admin Portal \u2192 Sites \u2192 YOUR_SITE \u2192 Resources<\/strong>, select <strong>Add a resource<\/strong>.<\/li>\n\n\n<li>Give it a name and enter an address such as <code>10.20.0.15<\/code>, <code>db.internal.example<\/code>, or <code>10.20.0.0\/24<\/code>. Use the narrowest address that meets your need.<\/li>\n\n\n<li>Open <strong>Policies<\/strong>, choose <strong>New Policy<\/strong>, then select the Resource and the user group that should access it. Save the policy.<\/li>\n\n\n<li>Download the Firezone Client from Firezone\u2019s official client page, sign in with the account or organization link, and connect to the Resource.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The Gateway host itself must be able to reach the Resource. Test that route from Debian before investigating the client if the destination is on a private network:<\/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 an HTTP service that is intentionally reachable. A response or an HTTP status proves the VPS can reach the service; it does not grant access to Firezone users until the policy is also present.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Firezone Gateway<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run these checks after connecting the client:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active firezone-gateway\nsudo ip link show tun-firezone\nsudo journalctl -u firezone-gateway -n 30 --no-pager<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output starts with <code>active<\/code>, shows a <code>tun-firezone<\/code> interface, and contains recent service entries without repeated authentication or connection errors. The portal should show the Gateway as online, and the Firezone Client should show the permitted Resource as connected.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From the test device, open the approved web service or connect to the approved SSH\/RDP address. Successful access confirms the whole chain: client identity, policy, Gateway tunnel, route, and the Resource\u2019s own firewall.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Build a private access gateway\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Debian 13 VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Build a private access gateway<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Deploy Firezone\u2019s WireGuard-based Gateway on a clean Debian 13 VPS.<\/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<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 list file and key do not match. Repeat the repository commands in Step 3, then run <code>sudo apt update<\/code> and check <code>apt-cache policy firezone-gateway<\/code>; an available candidate should come from <code>artifacts.firezone.dev<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>gpg: no valid OpenPGP data found<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The key download did not return a valid key, usually because DNS, outbound HTTPS, or a proxy blocked <code>artifacts.firezone.dev<\/code>. Check <code>getent hosts artifacts.firezone.dev<\/code> and <code>curl -I https:\/\/artifacts.firezone.dev\/apt\/key.gpg<\/code>, then fix the egress problem and rerun Step 3.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The Gateway remains offline after authentication<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Read the service log with <code>sudo journalctl -u firezone-gateway -n 50 --no-pager<\/code>. DNS failures, blocked outbound TCP 443, or a token that was already claimed are common causes; correct connectivity or create a fresh single-owner token in <strong>Sites \u2192 YOUR_SITE \u2192 Gateways<\/strong> and authenticate this host once.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The client connects but the Resource is unreachable<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check the address and policy first, then test the Resource directly from the VPS. The user must belong to the group selected in the policy, the Gateway must have a route to the destination, and the destination\u2019s firewall must permit 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>Restrict SSH at the VPS provider firewall to trusted source addresses and use SSH keys instead of password authentication.<\/li>\n\n\n<li>Treat <code>\/etc\/firezone<\/code> and the Gateway token as sensitive. Rotate the token in the portal if it is exposed, then update the Gateway and restart the service.<\/li>\n\n\n<li>For a repeatable SSH baseline, you can use VPSLake\u2019s <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">SSH hardening generator<\/a>, reviewing its output before applying it to a live server.<\/li>\n\n\n<li>Update the package periodically and confirm 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<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does Firezone create a web dashboard on Debian 13?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The Debian host runs the Gateway service, while administration happens in the hosted Firezone Admin Portal. You do not need to expose ports 80 or 443 for a local Firezone interface.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need Docker for Firezone on Debian 13?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The APT package installs the current Gateway directly as a systemd service, which is a simpler fit for a dedicated Debian VPS. Docker is a separate deployment option when you already manage container workloads.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is this the same as creating a manual <code>wg0<\/code> file?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Firezone manages the WireGuard-based data path, identity, and policy through its Gateway and Client. You define Sites, Resources, and Policies in the portal instead of distributing hand-written peer profiles.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why can\u2019t a connected user reach every private IP?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Firezone uses default-deny access: the user needs a Policy for the specific Resource. The Gateway also needs a working route to that address, and the destination network must allow the resulting traffic.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does Firezone create a web dashboard on Debian 13?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The Debian host runs the Gateway service, while administration happens in the hosted Firezone Admin Portal. You do not need to expose ports 80 or 443 for a local Firezone interface.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need Docker for Firezone on Debian 13?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The APT package installs the current Gateway directly as a systemd service, which is a simpler fit for a dedicated Debian VPS. Docker is a separate deployment option when you already manage container workloads.\"}}, {\"@type\": \"Question\", \"name\": \"Is this the same as creating a manual `wg0` file?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Firezone manages the WireGuard-based data path, identity, and policy through its Gateway and Client. You define Sites, Resources, and Policies in the portal instead of distributing hand-written peer profiles.\"}}, {\"@type\": \"Question\", \"name\": \"Why can\u2019t a connected user reach every private IP?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Firezone uses default-deny access: the user needs a Policy for the specific Resource. The Gateway also needs a working route to that address, and the destination network must allow the resulting traffic.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Firezone UI for WireGuard VPN on Debian 13 as a secure Gateway, connect a private resource, and verify access without Docker in minutes.","protected":false},"author":1,"featured_media":1146,"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":[98,146,148,147],"class_list":["post-1145","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-debian-13","tag-firezone","tag-vpn","tag-wireguard","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1145","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=1145"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1145\/revisions"}],"predecessor-version":[{"id":4158,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1145\/revisions\/4158"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1146"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1145"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1145"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}