Support
Need help? We've got you covered. See our support options below.
Knowledge base
Start here. Many questions can be answered by reading our docs.
Deployment Guide
A detailed, step-by-step guide for users setting up Firezone for the first time. Read this guide to learn how to deploy a production-grade Firezone setup.
Client apps
Installation and usage instructions for the Firezone Clients designed to be consumed by your workforce.
Troubleshooting guide
A comprehensive guide to help you troubleshoot common issues you may encounter using Firezone, including where to find logs and tips for debugging common issues.
FAQ
Some of our most frequently asked questions.
GitHub accountGitHub
Didn't find what you were looking for? We build Firezone in the open -- there's a good chance someone's already opened an issue.
Still need help?
Choose a support option below to get in touch with a Firezone team member.
| Option | Details | Wait time | Support hours |
|---|---|---|---|
| Send us an email | 1 - 2 business days | 24/7 | |
| Dedicated Slack channel | Available on Enterprise plans. Contact sales for details. | Under 8 hours | M-F |
| Community forums | https://github.com/firezone/firezone/discussions | ||
Diagnostic report
Run the diagnostic script on the affected machine to gather a comprehensive snapshot of its network state — including interface configuration, routing tables, DNS settings, VPN status, and recent system logs. Attaching the resulting archive to your support thread, along with a log export from the relevant client or gateway, can help the Firezone team more quickly diagnose your issue.
Run the following command in Terminal. The script will collect diagnostics and save a .tar.gz archive to your Desktop.
bash <(curl -fsSL https://www.firezone.dev/diag/macos.sh)Linux diagnostic script coming soon.
Windows diagnostic script coming soon.