-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: control/filtering/refresh | Network Error When more than 38 blacklists are active #2671
Comments
Hi, and thank you for your report. Could you please configure AdGuard Home to collect logs by setting |
Hi i have same error like that, 37 blacklist, this is the log https://raw.githubusercontent.com/dioey/AdGuard/main/adguad https://imgur.com/a/xxYDs3Q |
@dioey the link seems t obe invalid |
@ainar-g couldn't it be our POST body size limit shooting ourselves in the foot? |
sorry first time too post here the link https://raw.githubusercontent.com/dioey/AdGuard/main/adguad |
and here the screenshot https://imgur.com/N6GqUU7 |
Correction about the blocklist i have 27 not 37 |
@ameshkov, possibly. Investigating. |
Yes, I can do that. |
hem i dont use a proxy, but i use unbound as a recursive DNS server, is that a proxy? i using this tutorial from Pi-Hole, https://docs.pi-hole.net/guides/dns/unbound/ previous version never have this error |
Is there a way to switch to the previous version? |
The Same here. I use unbound. But with the previous version it worked without problems. |
If you followed the guide on our wiki, you can fist backup your AdGuard Home data and configuration, uninstall it, and then install it using the archive from v0.104.3 release page. |
Ok.thanks |
OK I downgrade to Previous version it work normally now 😁😁 |
Could you tell me how you did that ? |
First you need uninstall first, using terminal go to AdGuardHome folder, in my case in /opt/AdGuardHome/ then uninstall using command |
Am also back on AdGuard Home v0.104.3. |
I will post the log file here tomorrow, today it is not enough for me anymore |
It is also not possible for me to insert block lists from the following sources: Under AdGuard Home v0.104.3. this works without problems. |
Excuse me, but how can I provide you with the file? |
You need too edit 2 line on AdGuardHome.yaml by change the value |
Thanks a lot |
Where is the Debug.txt stored ? |
@merj1928 in my case in folder |
How can I upload the file here ? |
@ainar-g |
With or without unbound. The error occurs when you update the lists manually. |
Merge in DNS/adguard-home from 2671-timeout to master Updates #2671. Updates #2682. Squashed commit of the following: commit 79b1a36 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 15:25:26 2021 +0300 all: doc changes commit 84229b7 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 15:12:33 2021 +0300 home: imp names commit b18d7b0 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 15:04:27 2021 +0300 home: inc http timeouts
Seems the same as #2682, so I'll close this one as well. Please write new issues if you see any new errors. |
Merge in DNS/adguard-home from 2671-timeout to master Updates AdguardTeam#2671. Updates AdguardTeam#2682. Squashed commit of the following: commit 79b1a36 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 15:25:26 2021 +0300 all: doc changes commit 84229b7 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 15:12:33 2021 +0300 home: imp names commit b18d7b0 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Feb 15 15:04:27 2021 +0300 home: inc http timeouts
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details:
If more than 38 blacklists are active in AdGuard Home I get this error message:
Error: control/filtering/refresh | Network Error
Expected Behavior
Actual Behavior
If more than 38 blacklists are active in AdGuard Home I get this error message: Error: control/filtering/refresh | Network ErrorScreenshots
Screenshot:
Additional Information
The text was updated successfully, but these errors were encountered: