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’s WireGuard-based client.
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.
Prerequisites
- Debian 13 (Trixie), 64-bit, with a current kernel and a reachable internet connection.
- A root shell or a sudo-enabled account connected over SSH.
- 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.
- Network access from the VPS to the private resource you will publish through Firezone.
- A Firezone account, a browser for the Admin Portal, and a separate device on which to install the Firezone Client.
- No domain name or local TLS certificate is required for this Gateway deployment.
- A fresh VPSLake Linux VPS running Debian 13.
Step 1: Update Debian and check the host
Updating the base system and confirming the packet-filtering commands prevents an incomplete Gateway installation later.
sudo apt update
sudo apt full-upgrade -y
sudo apt install -y ca-certificates gnupg iptables wget
Check the release and the required firewall commands:
. /etc/os-release && printf '%s\n' "$PRETTY_NAME"
iptables --version
ip6tables --version
Expected output identifies Debian GNU/Linux 13 and prints an iptables v1.x version for both commands. If you are already logged in as root, remove sudo from the commands in this guide.
Step 2: Create a Firezone Site and Gateway token
The Site groups your Gateway with the resources it can reach, and its single-owner token registers this particular VPS.
- Sign in to the Firezone Admin Portal.
- Open Sites and select Add Site. Name it something recognizable, such as
Debian13-VPS, then save it. - From the new Site’s details page, choose Deploy a Gateway.
- Keep the Debian installation instructions open and copy the token into a password manager.
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.
Step 3: Install the Firezone Gateway package
The signed Firezone APT repository provides the Gateway binary and its systemd service without adding Docker or a local web stack.
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
Confirm that APT sees a candidate from the Firezone repository:
apt-cache policy firezone-gateway
The output should show an installed or candidate version and the artifacts.firezone.dev/apt repository. The official Debian deployment instructions use this repository and package name.
Step 4: Authenticate and start the Gateway
Authentication saves the Gateway identity locally and connects the service to the Site you created in the portal.
Run the interactive command:
sudo firezone-gateway authenticate
When prompted, paste the one-time token from Sites → YOUR_SITE → Deploy a Gateway. The command should register the VPS and create the firezone-gateway systemd service.
Check that systemd enabled and started it:
sudo systemctl is-enabled firezone-gateway
sudo systemctl is-active firezone-gateway
sudo systemctl status firezone-gateway --no-pager -l
Expected output includes:
enabled
active
Active: active (running)
Return to Firezone Admin Portal → Sites → YOUR_SITE. 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.
Step 5: Apply a narrow Debian firewall policy
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.
On a fresh server that does not already use another firewall, install and enable UFW like this:
sudo apt install -y ufw
sudo ufw allow OpenSSH
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw --force enable
sudo ufw status verbose
Expected output reports Status: active, allows 22/tcp through the OpenSSH 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.
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’s ports and protocols reference. Stateful cloud firewalls generally do not need a new inbound Firezone rule.
Step 6: Add a resource, policy, and client
An online Gateway only provides the path; a Resource and Policy decide what an authenticated user can actually reach.
- In Firezone Admin Portal → Sites → YOUR_SITE → Resources, select Add a resource.
- Give it a name and enter an address such as
10.20.0.15,db.internal.example, or10.20.0.0/24. Use the narrowest address that meets your need. - Open Policies, choose New Policy, then select the Resource and the user group that should access it. Save the policy.
- Download the Firezone Client from Firezone’s official client page, sign in with the account or organization link, and connect to the Resource.
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:
curl --connect-timeout 5 http://RESOURCE_IP:PORT/
Replace RESOURCE_IP and PORT 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.
Verify the Firezone Gateway
Run these checks after connecting the client:
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, shows a tun-firezone 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.
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’s own firewall.
Troubleshooting
Unable to locate package firezone-gateway
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 sudo apt update and check apt-cache policy firezone-gateway; an available candidate should come from artifacts.firezone.dev.
gpg: no valid OpenPGP data found
The key download did not return a valid key, usually because DNS, outbound HTTPS, or a proxy blocked artifacts.firezone.dev. Check getent hosts artifacts.firezone.dev and curl -I https://artifacts.firezone.dev/apt/key.gpg, then fix the egress problem and rerun Step 3.
The Gateway remains offline after authentication
Read the service log with sudo journalctl -u firezone-gateway -n 50 --no-pager. 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 Sites → YOUR_SITE → Gateways and authenticate this host once.
The client connects but the Resource is unreachable
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’s firewall must permit traffic from the Gateway path.
Hardening and maintenance
- Restrict SSH at the VPS provider firewall to trusted source addresses and use SSH keys instead of password authentication.
- Treat
/etc/firezoneand the Gateway token as sensitive. Rotate the token in the portal if it is exposed, then update the Gateway and restart the service. - For a repeatable SSH baseline, you can use VPSLake’s SSH hardening generator, reviewing its output before applying it to a live server.
- Update the package periodically and confirm the service after each upgrade:
sudo apt update
sudo apt install --only-upgrade firezone-gateway
sudo systemctl is-active firezone-gateway
FAQ
Does Firezone create a web dashboard on Debian 13?
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.
Do I need Docker for Firezone on Debian 13?
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.
Is this the same as creating a manual wg0 file?
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.
Why can’t a connected user reach every private IP?
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.