Skip to content
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 new! #2682

Closed
merj1928 opened this issue Feb 14, 2021 · 17 comments
Assignees
Milestone

Comments

@merj1928
Copy link

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • [x ] I am running the latest version
  • [x ] I checked the documentation and found no answer
  • [ x] I checked to make sure that this issue has not already been filed

Issue Details:

If more than 38 blacklists are active in AdGuard Home I get this error message:
Error: control/filtering/refresh | Network Error

  • Version of AdGuard Home server:
    • v0.105.0
  • How did you install AdGuard Home:
    • Raspberry Pi Guide here.
  • How did you setup DNS configuration:
    • Ubuntu Server, Asus RT AC68U Router
  • If it's a router or IoT, please write device model:
    • Raspberry Pi 3 Model B
  • Operating system and version:
    • Ubuntu Server (last)

Expected Behavior

Actual Behavior

If more than 38 blacklists are active in AdGuard Home I get this error message: Error: control/filtering/refresh | Network Error

Screenshots

Screenshot:

Additional Information

@merj1928
Copy link
Author

@DandelionSprout
Copy link
Member

It doesn't seem to me personally like the problem is universal to all AGH installations, as my setup on a Raspberry Pi 4 4GB has 39 blacklists and seems able to refresh as normal.

@dioey
Copy link

dioey commented Feb 15, 2021

@DandelionSprout it because unbound as DNS Resolver, AdGuard Home Version: 0.104.3 doesn't have this error, best solution for now is to stick with Version: 0.104.3

@DandelionSprout
Copy link
Member

DandelionSprout commented Feb 15, 2021

Okay, so it turns out I had 3 of my lists turned off at the time of testing. After adding 3 more lists on my end, I now receive the exact same error that the OP got.

@dioey
Copy link

dioey commented Feb 15, 2021

@DandelionSprout interesting, are using unbound too? I thought only who using unbound have this error, AdGuard Home v0.105.0 have a lot of bug

@DandelionSprout
Copy link
Member

I am not using Unbound that I know of.

@merj1928
Copy link
Author

@DandelionSprout interesting, are using unbound too? I thought only who using unbound have this error, AdGuard Home v0.105.0 have a lot of bug

With or without unbound. The error occurs when you update the lists manually.
However, it seems that they are updated during the automatic update.

@dioey
Copy link

dioey commented Feb 15, 2021

@merj1928 yeah I see the log filter update correctly, not sure what causing that error

adguard pushed a commit that referenced this issue Feb 15, 2021
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
@ainar-g
Copy link
Contributor

ainar-g commented Feb 15, 2021

@merj1928, @dioey, we've published some fixes in the new v0.105.1. It should be on all channels now. Please let us know if these fixes resolve or alleviate the issue. Thanks!

@merj1928
Copy link
Author

@merj1928, @dioey, we've published some fixes in the new v0.105.1. It should be on all channels now. Please let us know if these fixes resolve or alleviate the issue. Thanks!

All clear. Thank you very much.

@dioey
Copy link

dioey commented Feb 15, 2021

@ainar-g wow thanks it fixed now manual update filter no more error 😁😁

@merj1928
Copy link
Author

@merj1928, @dioey, we've published some fixes in the new v0.105.1. It should be on all channels now. Please let us know if these fixes resolve or alleviate the issue. Thanks!

The manual update, again brings the same error message

@merj1928
Copy link
Author

@ainar-g wow thanks it fixed now manual update filter no more error 😁😁

The manual update, again brings the same error message. ???

@dioey
Copy link

dioey commented Feb 15, 2021

@merj1928 I think it fixed now, the problem for me before is after update too version v0.105.0 it cant manual update the DNS Blocklist filter, but v0.105.1 already fix this problems

@DandelionSprout
Copy link
Member

I can confirm that v0.105.1-beta.1 fixed the problem on my end, if I'm not seeing completely wrong.

@merj1928
Copy link
Author

Ok after a reboot, it seems to work now.

@ainar-g
Copy link
Contributor

ainar-g commented Feb 16, 2021

Thank you all for testing! Please file new issues if you find anything wrong.

@ainar-g ainar-g closed this as completed Feb 16, 2021
heyxkhoa pushed a commit to heyxkhoa/AdGuardHome that referenced this issue Mar 20, 2023
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants