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.

Sign up for GitHub

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

Jump to bottom

v0.107.20 no longer recognizes enabled lists #5238

Closed
3 tasks done
timkgh opened this issue Dec 8, 2022 · 2 comments
Closed
3 tasks done

v0.107.20 no longer recognizes enabled lists #5238

timkgh opened this issue Dec 8, 2022 · 2 comments
Assignees
@ainar-g
Labels
bug P3: Medium
Milestone
v0.107.21

Comments

@timkgh
Copy link

timkgh commented Dec 8, 2022

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to report a bug and not ask a question

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

64-bit MIPS

Installation

GitHub releases or script from README

Setup

On a router, DHCP is handled by the router

AdGuard Home version

v0.107.20

Description

v0.107.20 UI no longer recognizes lists that are already enabled

E.g. all Security lists are enabled but when I click "Add blocklist" none of the checkboxes are checked.

image
@ainar-g
Copy link
Contributor

ainar-g commented Dec 8, 2022

Thanks for the report! This is probably caused by the same change that fixed the URLs of the vetted blocklists. We have changed the default lists to point to the same backup copies that AdGuard DNS uses, so for most blocklists you can just readd them or leave them as-is.

But the default lists' URLs haven't been properly updated, and we should fix that. We'll try to roll out the fix to the Edge channel soon.

@ainar-g ainar-g self-assigned this Dec 8, 2022
@ainar-g ainar-g added this to the v0.107.21 milestone Dec 8, 2022
adguard pushed a commit that referenced this issue Dec 8, 2022
@ainar-g
Pull request: 5238-default-filter-urls
8d453e7 
Updates #5238.

Squashed commit of the following:

commit 6a1b58b
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Thu Dec 8 14:18:54 2022 +0300

    all: upd go in github actions

commit 9836688
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Thu Dec 8 14:08:36 2022 +0300

    home: sync default filter urls
@ainar-g
Copy link
Contributor

ainar-g commented Jan 27, 2023

The default configuration has been fixed in v0.107.21. We've also added the way to fix the issue on older installations to the release notes.

@ainar-g ainar-g closed this as completed Jan 27, 2023
@ainar-g ainar-g modified the milestones: v0.107.23, v0.107.21 Jan 27, 2023
heyxkhoa pushed a commit to heyxkhoa/AdGuardHome that referenced this issue Mar 20, 2023
@ainar-g @heyxkhoa
Pull request: 5238-default-filter-urls
574a372 
Updates AdguardTeam#5238.

Squashed commit of the following:

commit 6a1b58b
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Thu Dec 8 14:18:54 2022 +0300

    all: upd go in github actions

commit 9836688
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Thu Dec 8 14:08:36 2022 +0300

    home: sync default filter urls
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ainar-g ainar-g

Labels
bug P3: Medium
Projects
None yet
Milestone
v0.107.21
Development

No branches or pull requests
2 participants
@ainar-g @timkgh