Troubleshooting Guide
Start with this guide for solutions to common issues faced by Firezone admins and end-users.
Gateway not connecting
If you're trying to deploy a new Gateway and it's not connecting, try running some of the troubleshooting commands below to diagnose the issue.
Check that the container is running:
docker ps --filter "name=firezone-gateway"
Check the container logs:
docker logs firezone-gateway
Check the status of the service:
sudo systemctl status firezone-gateway
Check the logs:
sudo journalctl -u firezone-gateway.service
Some browsers break DNS routing
Some web browsers enable DNS-over-HTTPS by default, which can interfere with Firezone's DNS-based routing system. If you're experiencing issues connecting to DNS Resources in your browser, or notice that DNS resources aren't being routed through a Firezone Gateway when they should be, try disabling DNS-over-HTTPS using the appropriate method below.
Firefox
- Go to
about:preferences#privacyin the address bar. - Scroll down to the "DNS over HTTPS" section.
- Ensure that "Off" is selected.
Chrome
- Go to
chrome://settings/securityin the address bar. - Scroll down to the "Advanced" section.
- Ensure that "Use secure DNS" is disabled.
Need additional help?
Try asking on one of our community-powered support channels:
- Discussion forums: Ask questions, report bugs, and suggest features.
- Discord server: Join discussions, meet other users, and chat with the Firezone team
- Email us: We read every message.