AdGuardHome AdGuard blocked local domain queries

Markfree

Regular Contributor
Today I had an issue with AdGuard where it was blocking queries for local domain hosts.
When I checked the dashboard, I noticed many blocks for local queries and they all pointed to the EasyList list.
AdGuard reported a block with rule ||o.
easylist_block.png

So, I tried to open EasyList and see if it had, somehow, that odd rule.
EasyList was very slow to open and its forum had some recent comments about a possible "large traffic" issue.

Also, I noticed the following message at AdGuard's log.
Code:
Oct 11 21:39:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:39:24.951551 [info] updated filter 1650265298: 3008217 bytes, 34051 rules
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.509979 [info] Couldn't fetch filter contents from URL https://easylist.to/easylist/easylist.txt, skipping: context deadline exceeded (Client.Timeout or context cancellation while reading body)
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.510103 [info] saving filter 1650265300 contents to: /tmp/mnt/entware/entware/etc/AdGuardHome/data/filters/1650265300.txt
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.510390 [info] Failed to update filter https://easylist.to/easylist/easylist.txt: context deadline exceeded (Client.Timeout or context cancellation while reading body)

But, of course, it did not have that specific rule.

The fact is that AdGuard somehow blocked my local domain because of EasyList issue.
After disabling EasyList list, it all went back to normal.

What I'm bugged about is that odd rule (||o) attributed to EasyList.
Any idea of what that is?
 

SomeWhereOverTheRainBow

Part of the Furniture
Today I had an issue with AdGuard where it was blocking queries for local domain hosts.
When I checked the dashboard, I noticed many blocks for local queries and they all pointed to the EasyList list.
AdGuard reported a block with rule ||o.
View attachment 44762
So, I tried to open EasyList and see if it had, somehow, that odd rule.
EasyList was very slow to open and its forum had some recent comments about a possible "large traffic" issue.

Also, I noticed the following message at AdGuard's log.
Code:
Oct 11 21:39:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:39:24.951551 [info] updated filter 1650265298: 3008217 bytes, 34051 rules
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.509979 [info] Couldn't fetch filter contents from URL https://easylist.to/easylist/easylist.txt, skipping: context deadline exceeded (Client.Timeout or context cancellation while reading body)
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.510103 [info] saving filter 1650265300 contents to: /tmp/mnt/entware/entware/etc/AdGuardHome/data/filters/1650265300.txt
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.510390 [info] Failed to update filter https://easylist.to/easylist/easylist.txt: context deadline exceeded (Client.Timeout or context cancellation while reading body)

But, of course, it did not have that specific rule.

The fact is that AdGuard somehow blocked my local domain because of EasyList issue.
After disabling EasyList list, it all went back to normal.

What I'm bugged about is that odd rule (||o) attributed to EasyList.
Any idea of what that is?
It sounds like something adguardhome developers need to troubleshoot. Something must be wrong when adguardhome is parsing the easy list. I would recommend opening an issue with adguardhome because clearly you have everything else setup right. It seems it only bugs out on you when you have their maintained filter list for EasyList toggled. Something definitely has to be wrong with how the list is being parsed.
 

SomeWhereOverTheRainBow

Part of the Furniture
Today I had an issue with AdGuard where it was blocking queries for local domain hosts.
When I checked the dashboard, I noticed many blocks for local queries and they all pointed to the EasyList list.
AdGuard reported a block with rule ||o.
View attachment 44762
So, I tried to open EasyList and see if it had, somehow, that odd rule.
EasyList was very slow to open and its forum had some recent comments about a possible "large traffic" issue.

Also, I noticed the following message at AdGuard's log.
Code:
Oct 11 21:39:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:39:24.951551 [info] updated filter 1650265298: 3008217 bytes, 34051 rules
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.509979 [info] Couldn't fetch filter contents from URL https://easylist.to/easylist/easylist.txt, skipping: context deadline exceeded (Client.Timeout or context cancellation while reading body)
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.510103 [info] saving filter 1650265300 contents to: /tmp/mnt/entware/entware/etc/AdGuardHome/data/filters/1650265300.txt
Oct 11 21:44:24 <hostname> AdGuardHome[5046]: 2022/10/11 21:44:24.510390 [info] Failed to update filter https://easylist.to/easylist/easylist.txt: context deadline exceeded (Client.Timeout or context cancellation while reading body)

But, of course, it did not have that specific rule.

The fact is that AdGuard somehow blocked my local domain because of EasyList issue.
After disabling EasyList list, it all went back to normal.

What I'm bugged about is that odd rule (||o) attributed to EasyList.
Any idea of what that is?

From what I can tell, I am not even able to access https://easylist.to/easylist/easylist.txt .

Adguardhome must not know how to respond when the filter list doesn't download properly. This definitly seems like an adguardhome bug you stumbled upon. Essentially, the bug is causing adguardhome to block with the filter you posted in the Query image.
 

SomeWhereOverTheRainBow

Part of the Furniture
@Markfree , if you would like, we could use this thread to record any similar "blocklist" issues in the future ( basically if the problem starts happening while using other filter lists as well). It is a great way to document. If it seems to be an on going concern, I will use the information provided here to open a well detailed report for adguardhome developer issue support.
 

Markfree

Regular Contributor
@Markfree , if you would like, we could use this thread to record any similar "blocklist" issues in the future ( basically if the problem starts happening while using other filter lists as well). It is a great way to document. If it seems to be an on going concern, I will use the information provided here to open a well detailed report for adguardhome developer issue support.
Sure. That's great.
Thanks
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top