Linux and gateway environments emphasize service management, permissions, transparent proxying, DNS, log rotation, and configuration backups. Their troubleshooting differs from desktop clients. Verify that the configuration loads from the command line before adding service management, then add log rotation, recovery at boot, and configuration backups. Expose the control interface only to trusted networks.
First confirm the deployment location
Determine whether the program starts through systemd, Docker, OpenWrt, or a manual command, and record the configuration directory, runtime user, listening ports, and network mode.
- Does it run through systemd, Docker, OpenWrt, or a manual command?
- Do the configuration and log directories have the required permissions?
- Do DNS and TUN/transparent proxying conflict with system networking?
- Is external-controller secured?
Configure for the environment
- Pin the core version and configuration directory(See Linux downloads)
- Verify that the configuration loads from the command line before adding service management
- Configure log rotation or limit the log level
- Restrict the Dashboard and external-controller to trusted networks
A gateway deployment affects every device on the network; save a rollback-ready configuration before changes
Insufficient router performance affects connection counts and DNS response time
Docker network mode affects TUN and transparent-proxy capabilities(See Advanced Networking FAQ)