-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
AdGuardHome
Sebastian Schmidt edited this page Jul 14, 2024
·
16 revisions
This is necessary to run AdGuardHome on port 25 (the default DNS port) otherwise AdGuardHome won't run. Choose one of the blow options
Learn more: https://adguard-dns.io/kb/adguard-home/getting-started/#running-without-superuser
setcap 'CAP_NET_BIND_SERVICE=+eip CAP_NET_RAW=+eip' /var/packages/adguardhome/target/bin/adguardhome
The schedule/command needs to be run every time after an AdGuardHome update.
If you are too late with running the command the update should roll back, you should be able to stop & start the package again to try the update again.
The following command (as root) only needs to be run after a SynCommunity package update
sed -i 's/package/root/g' /var/packages/adguardhome/conf/privilege
- Home
-
Packages
- Adminer
- Aria2
- Beets
- BicBucStriim
- Borgmatic
- cloudflared
- Comskip
- Debian Chroot
- Deluge
- Duplicity
- dnscrypt-proxy
- FFmpeg
- FFsync
- Flexget
- Gstreamer
- Google Authenticator
- Home Assistant Core
- Jellyfin
- Kiwix
- [matrix] Synapse homeserver
- MinIO
- Mono
- Mosh
- Mosquitto
- Node-Exporter
- Radarr/Sonarr/Lidarr/Jackett
- SaltStack
- SickBeard Custom
- SynoCLI-Disk
- SynoCLI-Devel
- SynoCLI-File
- SynoCLI-Kernel
- SynoCLI-Misc.
- SynoCLI-Monitor
- SynoCLI-NET
- Synogear
- Concepts
- Development
- Resources