I installed the new version and AdGuard Home stopped working. After downgrading with the same settings, it started working again:
adguardhome dnsproxy: handling request proto=tcp err="using request handler: strict conntrack mode: failed to get udp connection mark, blocking upstream query: conntrack query failed: netlink receive: numerical result out of range"
Any guidelines on that? The 4.7.7 firmware works perfectly.
So Iām not alone to have problem with AdguardHome on Flint 2 4.8.2.
DOH and DOT stopped working.
I get these king of log:
Sat Sep 6 09:29:38 2025 user.notice AdGuardHome[14168]: 2025/09/06 09:29:38.604858 Failed to get connection: netlink receive: numerical result out of range
Sat Sep 6 09:29:38 2025 kern.warn kernel: [54906.907666] netlink: 'AdGuardHome': attribute type 1 has an invalid length.
4.8.2 is a mess. Dnsmasq was changed and cause problems. Disappointing update. Im back on 4.7.7
Hi
We've tried to replicate the issue by upgrading a Flint 2 from firmware 4.7.7 to 4.8.2 with AdGuard Home configured/enabled, enable preserving configurations while upgrade, and we weren't able to reproduce it on our end.
The error message suggests that AdGuard Home is running into a problem.
To help us investigate this further, could you please share the specific configuration details for your AdGuard Home setup?
This will help us narrow down what might be causing the issue on device.
Hi
Thank you!
The AdGuard Home seems to be working but the clients that have encrypted dns (tested in 2 android phones) cannot connect to the Internet.
I have enable Encryption (HTTPS/QUIC/TLS), private server with dns over tls port, dns over qui port and with a valid SSL certificate.
I did the downgrade and everything started to working again.
Like the other user said, the DOH and DOT it's not working.
Hi,
Indeed, Adguard keeps handling āunsecuredā request received from LAN and Guest networks. Though encrypted DNS requests that comes from WAN (since I use a letsencrypt certificate) donāt suit anymore to android smartphones or web browsers.
(Iāve also got a custom nginx conf file to forward incoming https requests on port 443 to 192.168.8.1:9443. My Admin panel listen on another port)
It used to work great with v4.7.7.
Has AdguardHome been upgraded from v4.7.7 to 4.8.2 ?
I have some intermittent issue with DNS as well that started to happen around when I upgraded to this firmware. Rolling back with keeping the settings causes Internet to shut down completely. Upgrading again causes it to work. The issue I am experiencing is on Android, Windows Desktop and iOS. Browser throws a DNS error. When I retry a couple of times it's able to retrieve it.
Can GL-iNet create an script to export all settings (except the passwords/credentials) and then the user send it to the Support Team, that can load all settings to try to reproduce the issue?
Iām also having sporadic issues accessing the Internet after upgrading, and Iām running AdGuard with a few custom filters added and no other changes. I disabled the āAdGuard Home Handle Client Requestsā feature and it seems to make a big difference for me.
Thank you for sharing these leads with us.
Weāve been able to reproduce the issue on our side and confirmed that it happens when AdGuard Home is used as a DoH/DoT server.
Our R&D team has already been informed and will be looking into it further.
Thanks for getting onto this quickly. Hopefully you can release a new FW soon for OP24 as well as standard.
First of all thank you, that's fantastic news. What about the inability to roll back (with settings)? This is a massive risk. If that can't be fixed I won't be updating my firmware anytime soon after this release. I need to be able to roll back my firmware if there are critical bugs that make it into prod
You can linger update AdGuard Home any more on the new firmwares across the board also AdGuard Home is no longer in the AdGuard Directory Flint 2 & 3 going to try my GL-AXT1800 Slate AX as well i bet its the same also Specified Domain / IP List no longer works.
Please refer to our reply in the original post.
Any update? 
You can update AdGuard Home, from the GUI, on the Flint devices at least. You just need to remove a small piece of config from /etc/init.d/adguardhome file.
Paul
I had a similar issue when updating the device FW to 4.8.2, via the GUI although bizarrely, it looked to be just my TP-Link mesh APs that had dropped connection, despite picking up IP addresses. All wired devices āseemedā to work as expected.
Anyway, I used WinSCP to replace the AdGuard Home files (the files that are usually backed up had disappeared!). Then, and this was the important part, remove the config.yaml file from the device (/etc/AdGuardHome), start the service via the GUI and run through the initial OOTB set up. Once itās working, turn off the service again and copy the original config.yaml file back across to the device. Start the service up once more and it was now working as normal.
All credit to this guy: How to upgrade Adguard on the Flint, auto and manual? - #27 by admon
Paul
Our development team is still actively investigating and working on a fix for this issue.
In the meantime, if you would like to continue using firmware 4.8.2 with AdGuard Home, you can try a workaround.
Please try disabling the Encryption (HTTPS/QUIC/TLS) configuration in AdGuard Home and switch your client devices back to the original UDP DNS instead.
I assume that multipath is the issue, my script fixes it by running this command:
if ! grep -q 'procd_set_param env GODEBUG=multipathtcp=0' /etc/init.d/adguardhome; then
sed -i '/procd_set_param stderr 1/a\ procd_set_param env GODEBUG=multipathtcp=0' /etc/init.d/adguardhome
else
log "INFO" "Multipath TCP is already disabled in /etc/init.d/adguardhome"
return 0
fi
Never had any AGH issues on my 4.8.x firmware so far.
Yes you can on the older versions of firmware but not on the new ones thanks.
I can roll back to a stable firmware but not on the Flint 3 it hasnāt got one