AdGuardHome don't start at boot

Installing and Using OpenWrt
1

Bonjour

Change my router WRT32000ACM to BPI-3R to get fiber optic for futur use. No problem during installation except for AdguardHome package. After installation as per openwrt wiki , the program didn't start at boot. After investigation, found the problem with ntp program. The router lost some minute during boot.

Try to add ntp server to AdGuardHome and use ip for ntp server config still same problem. Decided to move starting position after sysntpd , position 99. That fixed my problem.

Question, moving AdGuardHome to starting position to 99 is OK or not a good solution ?

Thanks

2

It's a good solution.

3

Thanks for the info.

4

You'll experience a similar issue with the GL-MT6000 if you follow this guide, since it'll have you setup AdGuard Home to listen on br-lan (192.168.1.1). Then when you eventually reboot your router AdGuard Home will start too early, exit and then various things won't work correctly.

Configuring AdGuard Home to listen on all interfaces seems to work around the issue, but this pull request actually fixes the issue. However, I don't know if it'll ever be merged.

2 Likes
5

Compare my AGH init script with the pull request one. It's not merge. Copy the new init script to my router and fix the problem. Boot at position 19 and AGH work as expected.

6

That's good to hear. Hopefully the pull request is eventually merged so that the fix doesn't have to be manually applied every time you update OpenWrt.

7

I also have a R3 with OpenWrt 23.05.3 and have the same issue. What is meant by "starting position" and how should I change it?

8

edit at the adguard start script located in /etc/init.d,

there's a START= in the beginning of the file, change it to 99.

then stop, disable, reenable and start adguard again from system -> startup, in the webUI.

the start priority should move to 99.

1 Like
9

Stop is currently stated as "89": should that remain the same?

10

stop doesn't really matter.

1 Like
11

I had the same issue on the GL.iNet MT6000, the script posted above helped.

Is this going to be added on the next stable release so we don't have to do it every time we update?