Defguard Edge
Package installation
All release packages are available in the Defguard repository on GitHub on the releases page. The table below summarises the available options (X.Y.Z stands for a version).
Debian/Ubuntu
ARM64 (aarch64)
defguard-proxy-X.Y.Z-aarch64-unknown-linux-gnu.deb
Debian/Ubuntu
AMD64 (x86_64)
defguard-proxy-X.Y.Z-x86_64-unknown-linux-gnu.deb
Fedora/Red Hat/SUSE
ARM64 (aarch64)
defguard-proxy-X.Y.Z-aarch64-unknown-linux-gnu.rpm
Fedora/Red Hat/SUSE
AMD64 (x86_64)
defguard-proxy-X.Y.Z-x86_64-unknown-linux-gnu.rpm
FreeBSD
AMD64 (x86_64)
defguard-proxy-X.Y.Z_x86_64-unknown-freebsd.pkg
OPNsense (FreeBSD)
AMD64 (x86_64)
defguard-proxy-X.Y.Z_x86_64-unknown-opnsense.pkg
Choose the release you want to install, then download it either by using a web browser or with one of the commands below.
To download the package using wget, run:
wget <URL to the chosen package>For example:
wget https://github.com/DefGuard/proxy/releases/download/v2.0.0/defguard-proxy-2.0.0-x86_64-unknown-linux-gnu.debTo download the package using curl, run:
curl -OLf <URL to the chosen package>For example:
curl -OLf https://github.com/DefGuard/proxy/releases/download/v2.0.0/defguard-proxy-2.0.0-x86_64-unknown-linux-gnu.debOnce the package is downloaded, install it using the package tool appropriate for your operating system.
On Debian/Ubuntu:
On Fedora/Red Hat/SUSE:
On FreeBSD:
You can check whether Defguard Edge has been installed correctly:
Configuration
The Defguard Edge configuration file should be located at /etc/defguard/proxy.toml. An example configuration file looks as follows:
Service
The Defguard Edge package automatically installs its service definition. On Linux, it is in /usr/lib/systemd/system/defguard-proxy.service. On BSD, it is in /usr/local/etc/rc.d/defguard-proxy.
On Linux, the service is run as a dedicated defguard user with appropriate capabilities. The user is created automatically on package installation.
On BSD, the service runs as the root user.
If there are changes to the configuration file, the Defguard Edge service must be restarted.
On Linux:
On BSD:
Logs
On Linux, logs can be viewed using the journalctl command:
Was this helpful?