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.
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.
Prerequisites
- A fresh 64-bit Ubuntu 24.04 (Noble Numbat) VPS with working DNS and outbound internet access.
- Root access or a sudo-enabled user connected over SSH.
- At least 1 vCPU and 1 GB of RAM for a small Gateway. Add capacity for sustained traffic or many connected clients.
- A route from the VPS to the private Resource you want to publish through Firezone.
- A Firezone account, a browser for the Admin Portal, and a second device for testing the Firezone Client.
- 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.
- A fresh VPSLake Linux VPS running Ubuntu 24.04.
Step 1: Update Ubuntu and install the host tools
Updating Noble and installing the packet-filtering utilities gives the Gateway the host commands it checks during startup.
sudo apt update
sudo apt full-upgrade -y
sudo apt install -y ca-certificates gnupg iptables ufw wget
Confirm the release and both firewall command families before adding Firezone:
. /etc/os-release && printf '%s\n' "$PRETTY_NAME"
iptables --version
ip6tables --version
Expected output includes Ubuntu 24.04 and an iptables v1.x line for both IPv4 and IPv6. If your SSH session is already root, omit sudo from the commands below.
Step 2: Create a Firezone Site and Gateway token
The Site is the container for the Gateway and the private Resources it will serve; its single-owner token identifies this one VPS.
- Sign in at the Firezone Admin Portal or create an account.
- Open Sites → Add Site, name it something clear such as
Ubuntu-2404-Gateway, and save it. - On the Site details page, select Deploy a gateway and choose the Debian/Ubuntu installation method.
- Copy the displayed token into a password manager. You will paste it interactively in Step 4.
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.
Step 3: Install the Firezone Gateway package
The signed Firezone APT repository supplies the Gateway binary and its systemd service, so Ubuntu can receive future updates through its normal package workflow.
sudo install -d -m 0755 /etc/apt/keyrings
wget -qO- https://artifacts.firezone.dev/apt/key.gpg | sudo gpg --dearmor --yes -o /etc/apt/keyrings/firezone.gpg
echo "deb [signed-by=/etc/apt/keyrings/firezone.gpg] https://artifacts.firezone.dev/apt/ stable main" | sudo tee /etc/apt/sources.list.d/firezone.list > /dev/null
sudo apt update
sudo apt install -y firezone-gateway
This is the repository-based method in Firezone’s Debian and Ubuntu Gateway documentation. Check that APT has a candidate from the expected repository:
apt-cache policy firezone-gateway
The output should show an installed or candidate version and a source beginning with https://artifacts.firezone.dev/apt. If APT reports no candidate, stop here and use the first troubleshooting entry rather than downloading a random package.
Step 4: Authenticate and start the Gateway
Authentication associates the Ubuntu host with your Site; the service then maintains the connection after you close SSH or reboot the VPS.
Run the authenticator and paste the token only at its prompt:
sudo firezone-gateway authenticate
Now inspect the service and the interface created by the Gateway:
sudo systemctl is-active firezone-gateway
sudo systemctl status firezone-gateway --no-pager -l
sudo ip link show tun-firezone
Healthy output includes:
active
Active: active (running)
The final command should display a tun-firezone interface. Return to Firezone Admin Portal → Sites → Ubuntu-2404-Gateway and confirm that the Gateway is online.
Step 5: Lock down inbound traffic with UFW
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.
Keep your current SSH session open while enabling UFW. For the standard SSH port, allow SSH and deny unsolicited inbound traffic:
sudo ufw allow 22/tcp
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw --force enable
sudo ufw status verbose
Expected output shows Status: active, 22/tcp allowed, incoming traffic denied by default, and outgoing traffic allowed. If SSH listens on a different port, add sudo ufw allow YOUR_SSH_PORT/tcp before enabling the firewall and replace 22/tcp with that port.
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 49152-65535 range as described in Firezone’s ports and protocols reference. Do not add those as broad public inbound rules unless your own stateless network requires the documented return traffic.
Step 6: Add a Resource, Policy, and test client
An online Gateway provides connectivity but grants no access by itself; Firezone’s default-deny policy requires an explicit Resource and group rule.
- In Firezone Admin Portal → Sites → Ubuntu-2404-Gateway, select Add Resource.
- Give the Resource a name such as
Private-Appand enter its narrowest address: an IP, FQDN, or CIDR range such as10.20.0.15,db.internal.example, or10.20.0.0/24. - Open Policies → New Policy, choose the Resource and the user group that should reach it, then save the policy.
- Install the Firezone Client on a test device, sign in with your Firezone account slug, and connect to the permitted Resource.
First verify that the Gateway itself can reach an HTTP service at the destination:
curl --head --connect-timeout 5 http://RESOURCE_IP:RESOURCE_PORT/
Replace RESOURCE_IP and RESOURCE_PORT with a service that is intentionally reachable from the VPS. A response such as HTTP/1.1 200 OK proves the Ubuntu route works; it does not bypass the Firezone Policy.
Verify the Firezone Gateway
Run these checks after the test device reports that the Resource is connected:
sudo systemctl is-active firezone-gateway
sudo ip link show tun-firezone
sudo journalctl -u firezone-gateway -n 30 --no-pager
Expected output starts with active, includes the tun-firezone 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.
Troubleshooting
Unable to locate package firezone-gateway
APT did not load the Firezone repository, or the list file and signing key do not match. Re-run Step 3, then run sudo apt update and apt-cache policy firezone-gateway; a candidate should come from artifacts.firezone.dev.
gpg: no valid OpenPGP data found
The key request returned an error page or no data, usually because DNS, outbound HTTPS, or a proxy blocked artifacts.firezone.dev. Test name resolution and HTTPS, then fix the egress problem before repeating the repository commands:
getent hosts artifacts.firezone.dev
curl --head --fail https://artifacts.firezone.dev/apt/key.gpg
firezone-gateway is active but the portal shows Offline
Inspect the recent service messages with sudo journalctl -u firezone-gateway -n 50 --no-pager. A blocked outbound connection or an already-claimed token is common; confirm outbound access, then create a fresh token under Sites → YOUR_SITE → Deploy a gateway and authenticate this host once.
The client connects but the Resource cannot be reached
Check the Resource address and Policy group first. Then test the destination directly from Ubuntu; the Gateway needs a working route, and the Resource’s own firewall must permit traffic from the Gateway path. A Policy cannot repair a missing route or a blocked service port.
Hardening and maintenance
- Restrict SSH at the VPS provider firewall to trusted source addresses and use SSH keys instead of password authentication.
- Treat the Gateway token and
/var/lib/firezoneas sensitive. Rotate the token in the portal if it was exposed, then re-authenticate the host. - For a repeatable SSH baseline, review the output from VPSLake’s SSH hardening generator before applying it to a live server.
- Update the Gateway through APT and check the service after each upgrade:
sudo apt update
sudo apt install --only-upgrade firezone-gateway
sudo systemctl is-active firezone-gateway
FAQ
Does Ubuntu 24.04 host a Firezone web dashboard after installation?
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.
Do I need Docker or a separate WireGuard package?
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.
Can I connect to every private IP once the Client is online?
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.
Is a domain required for this Ubuntu Gateway?
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.