{"id":1149,"date":"2026-11-22T18:00:00","date_gmt":"2026-11-22T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1149"},"modified":"2026-11-22T18:00:00","modified_gmt":"2026-11-22T18:00:00","slug":"install-firezone-ui-wireguard-ubuntu-24-04","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/22\/install-firezone-ui-wireguard-ubuntu-24-04\/","title":{"rendered":"Install Firezone UI for WireGuard on Ubuntu 24.04"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">To install Firezone UI for WireGuard VPN on Ubuntu 24.04, deploy a Firezone Gateway and control it from the hosted Admin Portal. In roughly 10 minutes, your VPS can give approved users access to a private server, application, database, or subnet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The current Firezone design separates the control plane from the Gateway. Ubuntu runs the WireGuard-based data path, while the portal manages Sites, users, Resources, and Policies; you do not need to expose a local Firezone dashboard.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>A fresh 64-bit Ubuntu 24.04 (Noble Numbat) VPS with working DNS and outbound internet access.<\/li>\n\n\n<li>Root access or a sudo-enabled user connected over SSH.<\/li>\n\n\n<li>At least 1 vCPU and 1 GB of RAM for a small Gateway. Add capacity for sustained traffic or many connected clients.<\/li>\n\n\n<li>A route from the VPS to the private Resource you want to publish through Firezone.<\/li>\n\n\n<li>A Firezone account, a browser for the Admin Portal, and a second device for testing the Firezone Client.<\/li>\n\n\n<li>No domain name or local TLS certificate is required for the Gateway. A domain may still be needed by the application you publish as a Resource.<\/li>\n\n\n<li>A fresh <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> running Ubuntu 24.04.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Update Ubuntu and install the host tools<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Updating Noble and installing the packet-filtering utilities gives the Gateway the host commands it checks during startup.<\/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 ufw wget<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Confirm the release and both firewall command families before adding Firezone:<\/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>Ubuntu 24.04<\/code> and an <code>iptables v1.x<\/code> line for both IPv4 and IPv6. If your SSH session is already root, omit <code>sudo<\/code> from the commands below.<\/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 is the container for the Gateway and the private Resources it will serve; its single-owner token identifies this one VPS.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Sign in at the <a href=\"https:\/\/app.firezone.dev\/\" target=\"_blank\" rel=\"noopener\">Firezone Admin Portal<\/a> or create an account.<\/li>\n\n\n<li>Open <strong>Sites \u2192 Add Site<\/strong>, name it something clear such as <code>Ubuntu-2404-Gateway<\/code>, and save it.<\/li>\n\n\n<li>On the Site details page, select <strong>Deploy a gateway<\/strong> and choose the Debian\/Ubuntu installation method.<\/li>\n\n\n<li>Copy the displayed token into a password manager. You will paste it interactively in Step 4.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Use a separate token for every Gateway. Do not store this credential in a repository, ticket, screenshot, or shell history; a single-owner token is claimed by the first Gateway that connects with it.<\/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 supplies the Gateway binary and its systemd service, so Ubuntu can receive future updates through its normal package workflow.<\/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\">This is the repository-based method in Firezone\u2019s <a href=\"https:\/\/www.firezone.dev\/kb\/deploy\/debian\" target=\"_blank\" rel=\"noopener\">Debian and Ubuntu Gateway documentation<\/a>. Check that APT has a candidate from the expected 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 a source beginning with <code>https:\/\/artifacts.firezone.dev\/apt<\/code>. If APT reports no candidate, stop here and use the first troubleshooting entry rather than downloading a random package.<\/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 associates the Ubuntu host with your Site; the service then maintains the connection after you close SSH or reboot the VPS.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the authenticator and paste the token only at its prompt:<\/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 inspect the service and the interface created by the Gateway:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active firezone-gateway\nsudo systemctl status firezone-gateway --no-pager -l\nsudo ip link show tun-firezone<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Healthy output includes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>active\nActive: active (running)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The final command should display a <code>tun-firezone<\/code> interface. Return to <strong>Firezone Admin Portal \u2192 Sites \u2192 Ubuntu-2404-Gateway<\/strong> and confirm that the Gateway is online.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Lock down inbound traffic with UFW<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Gateway initiates its control-plane and tunnel connections, so the VPS does not need public ports 80, 443, or a manually configured WireGuard listener.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep your current SSH session open while enabling UFW. For the standard SSH port, allow SSH and deny unsolicited inbound traffic:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ufw allow 22\/tcp\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 <code>Status: active<\/code>, <code>22\/tcp<\/code> allowed, incoming traffic denied by default, and outgoing traffic allowed. If SSH listens on a different port, add <code>sudo ufw allow YOUR_SSH_PORT\/tcp<\/code> before enabling the firewall and replace <code>22\/tcp<\/code> with that port.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With the normal stateful VPS firewall, the default outbound policy is enough. If your provider or an upstream firewall filters egress, allow outbound TCP 443, UDP 3478, and the UDP <code>49152-65535<\/code> range as described in Firezone\u2019s <a href=\"https:\/\/www.firezone.dev\/kb\/reference\/ports\" target=\"_blank\" rel=\"noopener\">ports and protocols reference<\/a>. Do not add those as broad public inbound rules unless your own stateless network requires the documented return traffic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Add a Resource, Policy, and test client<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An online Gateway provides connectivity but grants no access by itself; Firezone\u2019s default-deny policy requires an explicit Resource and group rule.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>In <strong>Firezone Admin Portal \u2192 Sites \u2192 Ubuntu-2404-Gateway<\/strong>, select <strong>Add Resource<\/strong>.<\/li>\n\n\n<li>Give the Resource a name such as <code>Private-App<\/code> and enter its narrowest address: an IP, 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 New Policy<\/strong>, choose the Resource and the user group that should reach it, then save the policy.<\/li>\n\n\n<li>Install the Firezone Client on a test device, sign in with your Firezone account slug, and connect to the permitted Resource.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">First verify that the Gateway itself can reach an HTTP service at the destination:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl --head --connect-timeout 5 http:\/\/RESOURCE_IP:RESOURCE_PORT\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>RESOURCE_IP<\/code> and <code>RESOURCE_PORT<\/code> with a service that is intentionally reachable from the VPS. A response such as <code>HTTP\/1.1 200 OK<\/code> proves the Ubuntu route works; it does not bypass the Firezone Policy.<\/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 the test device reports that the Resource is connected:<\/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>, includes the <code>tun-firezone<\/code> interface, and shows recent log entries without repeated authentication, DNS, or connection errors. The Admin Portal should list the Gateway as online. From the test device, open the approved web service or connect to the approved SSH\/RDP address; that confirms the client, Policy, Gateway, route, and destination firewall work together.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Deploy Firezone securely\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Ubuntu 24.04 VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Deploy Firezone securely<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Run a WireGuard-based Firezone Gateway on a clean Ubuntu 24.04 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 did not load the Firezone repository, or the list file and signing key do not match. Re-run Step 3, then run <code>sudo apt update<\/code> and <code>apt-cache policy firezone-gateway<\/code>; a 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 request returned an error page or no data, usually because DNS, outbound HTTPS, or a proxy blocked <code>artifacts.firezone.dev<\/code>. Test name resolution and HTTPS, then fix the egress problem before repeating the repository commands:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>getent hosts artifacts.firezone.dev\ncurl --head --fail https:\/\/artifacts.firezone.dev\/apt\/key.gpg<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><code>firezone-gateway<\/code> is active but the portal shows Offline<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Inspect the recent service messages with <code>sudo journalctl -u firezone-gateway -n 50 --no-pager<\/code>. A blocked outbound connection or an already-claimed token is common; confirm outbound access, then create a fresh token under <strong>Sites \u2192 YOUR_SITE \u2192 Deploy a gateway<\/strong> and authenticate this host once.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The client connects but the Resource cannot be reached<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check the Resource address and Policy group first. Then test the destination directly from Ubuntu; the Gateway needs a working route, and the Resource\u2019s own firewall must permit traffic from the Gateway path. A Policy cannot repair a missing route or a blocked service port.<\/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 the Gateway token and <code>\/var\/lib\/firezone<\/code> as sensitive. Rotate the token in the portal if it was exposed, then re-authenticate the host.<\/li>\n\n\n<li>For a repeatable SSH baseline, review the output from VPSLake\u2019s <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">SSH hardening generator<\/a> before applying it to a live server.<\/li>\n\n\n<li>Update the Gateway through APT and check 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 Ubuntu 24.04 host a Firezone web dashboard after installation?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The VPS runs the Gateway service and the hosted Admin Portal manages the Firezone configuration. You should not expose a local Firezone login page on ports 80 or 443 for this setup.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need Docker or a separate WireGuard package?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The Ubuntu APT package installs the Gateway as a systemd service and manages the WireGuard-based data path. Docker is a separate deployment choice, and a hand-written <code>wg0<\/code> profile is not needed here.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I connect to every private IP once the Client is online?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Firezone uses default-deny access, so the user must belong to a group allowed by a Policy for the requested Resource. The Gateway must also be able to route to that address, and the destination firewall must allow the traffic.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is a domain required for this Ubuntu Gateway?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The Gateway connects outbound to Firezone and does not publish a local HTTPS control panel. A domain may be appropriate for a private web application, but it is not an installation requirement for the Gateway itself.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does Ubuntu 24.04 host a Firezone web dashboard after installation?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The VPS runs the Gateway service and the hosted Admin Portal manages the Firezone configuration. You should not expose a local Firezone login page on ports 80 or 443 for this setup.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need Docker or a separate WireGuard package?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The Ubuntu APT package installs the Gateway as a systemd service and manages the WireGuard-based data path. Docker is a separate deployment choice, and a hand-written `wg0` profile is not needed here.\"}}, {\"@type\": \"Question\", \"name\": \"Can I connect to every private IP once the Client is online?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Firezone uses default-deny access, so the user must belong to a group allowed by a Policy for the requested Resource. The Gateway must also be able to route to that address, and the destination firewall must allow the traffic.\"}}, {\"@type\": \"Question\", \"name\": \"Is a domain required for this Ubuntu Gateway?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The Gateway connects outbound to Firezone and does not publish a local HTTPS control panel. A domain may be appropriate for a private web application, but it is not an installation requirement for the Gateway itself.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Firezone UI for WireGuard VPN on Ubuntu 24.04 as a Gateway, secure SSH with UFW, and verify private resource access in about 10 minutes.","protected":false},"author":1,"featured_media":1150,"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":[146,102,148,147],"class_list":["post-1149","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-firezone","tag-ubuntu-24-04","tag-vpn","tag-wireguard","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1149","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=1149"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1149\/revisions"}],"predecessor-version":[{"id":4164,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1149\/revisions\/4164"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1150"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1149"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1149"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1149"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}