Package Details: adguardhome 1:0.107.7-1

Git Clone URL: (read-only, click to copy)
Package Base: adguardhome
Description: Network-wide ads and trackers blocking DNS server
Upstream URL:
Keywords: adblocker blocker dns
Licenses: GPL
Submitter: graysky
Maintainer: anonfunc
Last Packager: anonfunc
Votes: 16
Popularity: 1.16
First Submitted: 2019-12-22 11:00 (UTC)
Last Updated: 2022-06-08 09:49 (UTC)

Pinned Comments

anonfunc commented on 2022-03-22 14:03 (UTC) (edited on 2022-06-08 19:58 (UTC) by anonfunc)

If you come from ≤0.107.5-1: Systemd service has been renamed from AdGuardHome to adguardhome. You need to re-enable it after the update.

systemctl disable AdGuardHome && systemctl enable adguardhome

Latest Comments

anonfunc commented on 2022-03-22 14:03 (UTC) (edited on 2022-06-08 19:58 (UTC) by anonfunc)

If you come from ≤0.107.5-1: Systemd service has been renamed from AdGuardHome to adguardhome. You need to re-enable it after the update.

systemctl disable AdGuardHome && systemctl enable adguardhome

Flat commented on 2021-12-26 18:43 (UTC)

@anonfunc That does build without issues.

xyzabc123 commented on 2021-12-26 18:39 (UTC) (edited on 2021-12-26 22:31 (UTC) by xyzabc123)

@anonfunc: You are correct. I didn't notice the problem because I depend on nodejs-lts-gallium on my current setup.

@Flat @gleb.zhulik: Please consider filing a bug upstream

@all: Merry Christmas Everyone

anonfunc commented on 2021-12-26 17:10 (UTC)

@Flat Try building with nodejs-lts-gallium.

Flat commented on 2021-12-26 16:47 (UTC) (edited on 2021-12-26 16:49 (UTC) by Flat)

This version doesn't build for me as well, in a clean chroot. Same 58 errors.

xyzabc123 commented on 2021-12-22 11:44 (UTC)

@gleb.zhulik: Yes builds and runs fine on my arch box.

gleb.zhulik commented on 2021-12-22 11:36 (UTC) (edited on 2021-12-22 11:38 (UTC) by gleb.zhulik)

Hello, does it really build on your computer? I'm getting 58 errors while compiling the frontend, all the same but for different files:

hexchain commented on 2021-11-16 15:58 (UTC)

The currently released version is not compatible with Go 1.17. Replacing quic-go v0.20.1 with v0.21.1 in go.mod seems to work.

graysky commented on 2021-05-06 23:05 (UTC)

Good, thanks for pointing out the fix.

xyzabc123 commented on 2021-05-06 22:59 (UTC)

@graysky - Working as expected, thanks.

graysky commented on 2021-05-06 22:47 (UTC)

@setBollean - Good observation. Please try 0.106.2-2 and let me know if it worked.

xyzabc123 commented on 2021-05-06 21:21 (UTC) (edited on 2021-05-06 21:23 (UTC) by xyzabc123)

Changing make -j1 CHANNEL=release VERBOSE=1 to make -j1 CHANNEL=release VERBOSE=1 VERSION=v0.106.2 in PKGBUILD fixes the issue. I just checked all versions back to v0.105.2 and the source tarballs always seem to include VERSION = v0.0.0 in the Makefile. I'am not sure if I never noticed that or the update banner in the web interface is new.

xyzabc123 commented on 2021-05-06 21:07 (UTC)

@graysky: Strange the precompiled build AdGuardHome_linux_amd64.tar.gz returns AdGuard Home, version v0.106.2. I will poke around a bit and report back.

graysky commented on 2021-05-06 20:08 (UTC)

I don't think this is a function of packaging. You might consider opening a case upstream.

xyzabc123 commented on 2021-05-06 19:11 (UTC)

Since the latest release I get a banner in the web interface saying an update to v0.106.2 is available. Running the binary with --version results in AdGuard Home, version v0.0.0.

chrboesch commented on 2021-04-30 21:19 (UTC)

Yes, thank you!

graysky commented on 2021-04-30 18:05 (UTC)

@chrboesch - does 0.106.1-2 work for you?

chrboesch commented on 2021-04-30 17:45 (UTC)

Please set the CHANNEL macro to 'release' when invoking make, see script documentation:

mvidaldp commented on 2021-03-18 12:26 (UTC) (edited on 2021-03-18 12:26 (UTC) by mvidaldp)

@graysky I actually did not manage to build it on aarch64 since the version 0.105.x Before it worked like a charm (until 0.104.x). I just wanted to point out that there is an alternative in case the build does not work for someones else, not blaming you :) Plus, it takes quite a lot of time and storage to build it. So it is definitely convenient to consider the binary package if you want to install it on a raspberry pi, for instance.

graysky commented on 2021-03-16 18:06 (UTC)

This packages builds fine on armv7h, aarch64, and x86_64. If someone is building this package, they want to do so from source. No sure why you're advertising the binary package here.

mvidaldp commented on 2021-03-16 14:35 (UTC)

In case you have problems building it for arm architectures, consider adguardhome's binary AUR package:

graysky commented on 2021-03-07 22:39 (UTC)

Thanks for letting me know.

xyzabc123 commented on 2021-03-07 22:17 (UTC)


Working as expected, thanks.

graysky commented on 2021-03-07 22:08 (UTC)

@setboolean - Please try 0.105.1-2 and report back.

xyzabc123 commented on 2021-03-07 21:58 (UTC)


To the AdGuardHome.service unit.


Upstream Issue:

graysky commented on 2021-03-07 20:28 (UTC)

@setboolean - Added to ...?

xyzabc123 commented on 2021-03-07 14:23 (UTC)

CAP_NET_RAW needs to be added to the capability set for the DHCP Server to work.

xyzabc123 commented on 2021-03-05 02:12 (UTC) (edited on 2021-03-07 12:51 (UTC) by xyzabc123)

I'm getting the following error during the build process. Can anybody offer some guidance?

==> Starting build()...
npm --prefix client ci
npm ERR! semver.simplifyRange is not a function

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/xxx/.npm/_logs/2021-03-05T02_10_42_102Z-debug.log
make: *** [Makefile:69: js-deps] Error 1
==> ERROR: A failure occurred in build().
error making: adguardhome


Seemed to be problem with npm on my side.


Delete $user/.npm folders. Run npm clean cache --force. Build AdGuardHome as usual.

diegoduarte commented on 2021-02-11 22:33 (UTC)

@graysky the issue was resolved using 2GB of memory RAM on this VM

diegoduarte commented on 2021-02-11 16:04 (UTC)

@graysky Maybe, I have only 1GB of memory RAM available for this VM, but this OOM issue never happened before

graysky commented on 2021-02-11 14:13 (UTC)

You should not need to adjust your MAKEFLAGS. The PKGBUILD will do that. 1:0.105.0-3 builds for me in a clean chroot. Is this something in your environment? Are you out of physical memory?

diegoduarte commented on 2021-02-11 13:15 (UTC)

@graysky Using MAKEFLAGS "make -j1" I got "JavaScript heap out of memory" on the building process

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 0x5613e1123fd1 node::Abort() [webpack] 2: 0x5613e1042144 node::FatalError(char const, char const) [webpack] 3: 0x5613e1303d62 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, bool) [webpack] 4: 0x5613e1303fc8 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, bool) [webpack] 5: 0x5613e14c3c36 [webpack] 6: 0x5613e14c3d8c [webpack] 7: 0x5613e14d1c4f v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [webpack] 8: 0x5613e14d2487 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack] 9: 0x5613e14d5b2c v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack] 10: 0x5613e14d5b94 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack] 11: 0x5613e149ad3b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack] 12: 0x5613e17e1bfa v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long, v8::internal::Isolate) [webpack] 13: 0x5613e1b3b779 [webpack] error Command failed with signal "SIGABRT". info Visit for documentation about this command. make: *** [Makefile:67: js-build] Error 1 ==> ERROR: A failure occurred in build(). Aborting... :: yarn is now an orphan package :: failed to build adguardhome package(s)

graysky commented on 2021-02-11 12:44 (UTC)

@diegoduarte -

EDIT: workaround is building with make -j1 which is now hard-coded into the PKGBUILD until upstream addresses it. Enjoy.

diegoduarte commented on 2021-02-11 11:09 (UTC)

@graysky I got the following error on the last release (1:0.105.0-1)

:: Building adguardhome package(s)... ==> Making package: adguardhome 1:0.105.0-1 (Thu 11 Feb 2021 11:05:40 AM WET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Removing existing $pkgdir/ directory... ==> Starting build()... npm --prefix client ci

added 1828 packages, and audited 1829 packages in 23s

13 vulnerabilities (10 low, 3 high)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

Run npm audit for details. yarn --cwd client2 install make: yarn: No such file or directory make: *** [Makefile:70: js-deps] Error 127 ==> ERROR: A failure occurred in build(). Aborting... :: failed to build adguardhome package(s)

graysky commented on 2020-10-30 09:57 (UTC)

@frantic - I think an epoch= is required here or we wait for a version that is greater than 0.104.0.

frantic1048 commented on 2020-10-30 09:37 (UTC)

According to latest version change from 0.104.0.beta3-1 to 0.104.0-1.

I found vercmp 0.104.0-1 0.104.0.beta3-1 returns -1, which means pacman thinks 0.104.0-1 is an older version compared to 0.104.0.beta3-1. May we bump a new pkgver to fix this?

graysky commented on 2020-08-01 10:48 (UTC)

@bhyoo - This is not a binary package.

bhyoo commented on 2020-08-01 03:59 (UTC)

@graysky How about just using official binaries?? They have updated Makefile and github action to build binaries for several platforms.

graysky commented on 2020-07-31 10:00 (UTC)

I am having problems building a new make dependence, golangci-lint. So I cannot yet update this package.

graysky commented on 2020-07-31 10:00 (UTC) (edited on 2020-07-31 10:01 (UTC) by graysky)

@laggardkernel - This is been fixing in 0.103.3 but see the readme.install which should work-around for 0.102.

laggardkernel commented on 2020-07-31 02:26 (UTC) (edited on 2020-07-31 02:49 (UTC) by laggardkernel)

[fatal] Couldn't start forwarding DNS server, cause: couldn't listen to UDP socket, cause: listen udp bind: permission denied

Any solution?

remove "-s run" fixed my problem.

broken.pipe commented on 2020-04-27 07:40 (UTC)

Thanks for the package! Would you mind shipping it within your repo-ck repository (or any other if available)? 600 MB build dependencies for a 6 MB package is a bit much!

graysky commented on 2020-04-20 18:00 (UTC)

@bhyoo - Please check 0.101.0-2

bhyoo commented on 2020-04-20 17:03 (UTC)

Hi, Thanks for your contribution. Could you please move User and Group into Service in AdGuardHome.service?

gleb.zhulik commented on 2020-04-15 20:53 (UTC)

The app built using this PKGBUILD via pikaur does not know it's version and returns an empty string.

I opened an issue:

graysky commented on 2020-03-13 14:59 (UTC)

@superbil - You can package a statically linked binary (see mprime vs mprime-bin). This package will allow you to build from source.

Superbil commented on 2020-03-13 14:14 (UTC)


AUR can't use binary, must use source code

graysky commented on 2020-01-01 15:47 (UTC)

That is a pre-compiled binary. This allows you to build your own.

j1simon commented on 2020-01-01 14:50 (UTC) (edited on 2020-01-01 14:52 (UTC) by j1simon)

Is it not better (and easy and fast) install the bin package released: <>$pkgver/AdGuardHome_linux_amd64.tar.gz ?

# Maintainer graysky <graysky AT archlinux DOT us>
pkgdesc="Network-wide ads and trackers blocking DNS server"

package() {
  install -Dm755 "$_pkgname/$_pkgname" "$pkgdir/var/lib/adguardhome/$_pkgname"
  install -Dm644 "$_pkgname.service" "$pkgdir/usr/lib/systemd/system/$_pkgname.service"

In fact, the version in this PKGBUILD is outdated.