starred/AdGuardHome

Fork 0

mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2026-03-04 00:01:12 -05:00

Whitelist & temp disable blocking for unprivileged clients #1146

New issue

Open

opened 2026-03-04 01:06:02 -05:00 by deekerman · 7 comments

deekerman commented

2026-03-04 01:06:02 -05:00

Owner

Originally created by @rodalpho on GitHub (Dec 5, 2019).

One major problem with DNS-based adblockers is that unprivileged clients have no way to whitelist or disable adblocking to fix page damage on their own. This responsibility all falls to the server admin, unless they give admin access to everybody.

Since AG Home has the ability to set DNS on a per-client basis, it should be possible to fix that. This would be a killer feature differentiating AGH from Pihole. My thoughts are:

Client goes to "https://adguard". Ideally this would be a configurable local hostname that always works. This page is separate from the full admin site with limited privileges.

If parental control is off, this site is accessible without any authentication. Otherwise it requires a password shared between all (adult) clients.

The (adult) client is permitted to white/blacklist hosts and/or disable blocking for a configurable period of time, all affecting that client only. Per-client configurations persist and are saved by MAC address.
That's it!

Originally created by @rodalpho on GitHub (Dec 5, 2019). One major problem with DNS-based adblockers is that unprivileged clients have no way to whitelist or disable adblocking to fix page damage on their own. This responsibility all falls to the server admin, unless they give admin access to everybody. Since AG Home has the ability to set DNS on a per-client basis, it should be possible to fix that. This would be a _killer_ feature differentiating AGH from Pihole. My thoughts are: 1) Client goes to "https://adguard". Ideally this would be a configurable local hostname that always works. This page is separate from the full admin site with limited privileges. If parental control is off, this site is accessible without any authentication. Otherwise it requires a password shared between all (adult) clients. 2) The (adult) client is permitted to white/blacklist hosts and/or disable blocking for a configurable period of time, all affecting that client only. Per-client configurations persist and are saved by MAC address. 3) That's it!

deekerman added the

feature request

P3: Medium

labels

2026-03-04 01:06:02 -05:00

deekerman commented

2026-03-04 01:06:04 -05:00

Author

Owner

@ghost commented on GitHub (Dec 7, 2019):

Refer below feature requests then possible consider as duplicate.

@ghost commented on GitHub (Dec 7, 2019): Refer below feature requests then possible consider as duplicate. - https://github.com/AdguardTeam/AdGuardHome/issues/997 - https://github.com/AdguardTeam/AdGuardHome/issues/435 - https://github.com/AdguardTeam/AdGuardHome/issues/1203 https://github.com/AdguardTeam/AdGuardHome/issues/951

deekerman commented

2026-03-04 01:06:04 -05:00

Author

Owner

@ameshkov commented on GitHub (Dec 8, 2019):

@ArchiveBase this is not really a duplicate. Basically what's requested is a simplified "client" web panel where the client can change its settings (without changing the global settings).

@ameshkov commented on GitHub (Dec 8, 2019): @ArchiveBase this is not really a duplicate. Basically what's requested is a simplified "client" web panel where the client can change its settings (without changing the global settings).

deekerman commented

2026-03-04 01:06:04 -05:00

Author

Owner

@ghost commented on GitHub (Dec 8, 2019):

@ameshkov then it's a one thing explained in https://github.com/AdguardTeam/AdGuardHome/issues/997 😉

Configure administrator access to certain 'Client' #809 for manage data and change settings (change DNS #821 and filters #435 etc)

@ghost commented on GitHub (Dec 8, 2019): @ameshkov then it's a one thing explained in https://github.com/AdguardTeam/AdGuardHome/issues/997 😉 > Configure administrator access to certain 'Client' #809 for manage data and change settings (change DNS #821 and filters #435 etc)

deekerman commented

2026-03-04 01:06:05 -05:00

Author

Owner

@rodalpho commented on GitHub (Dec 9, 2019):

I think there is an amount of overlap, the key difference being that I didn't envision nonprivileged clients being required to create and manage a user account, instead just tracking by MAC address. These are unsophisticated users and my primary goal was to remove as much complexity as possible while allowing them to easily correct page damage.

@rodalpho commented on GitHub (Dec 9, 2019): I think there is an amount of overlap, the key difference being that I didn't envision nonprivileged clients being required to create and manage a user account, instead just tracking by MAC address. These are unsophisticated users and my primary goal was to remove as much complexity as possible while allowing them to easily correct page damage.

deekerman commented

2026-03-04 01:06:05 -05:00

Author

Owner

@ghost commented on GitHub (Dec 9, 2019):

Usually those simple features ruin the software quality, conflict or lack compatibility for new features. Even it reduce the complexity as you expected, there are cons may lead to find alternatives with time.

Without especially point out, you mention about things belong to user account as incomplete however seems not perfect for me. that's why i explained it.

@rodalpho dont take that serious😊 just only a feedback for @ameshkov😉

@ghost commented on GitHub (Dec 9, 2019): Usually those simple features ruin the software quality, conflict or lack compatibility for new features. Even it reduce the complexity as you expected, there are cons may lead to find alternatives with time. Without especially point out, you mention about things belong to user account as incomplete however seems not perfect **for me**. that's why i explained it. @rodalpho dont take that serious😊 just only a feedback for @ameshkov😉

deekerman commented

2026-03-04 01:06:05 -05:00

Author

Owner

@rodalpho commented on GitHub (Dec 10, 2019):

I don't have any real insight into where AGH is going so I can't comment on conflicts or compatibility in the future, I just described a feature that would be very useful to my users who constantly complain about page damage.

@rodalpho commented on GitHub (Dec 10, 2019): I don't have any real insight into where AGH is going so I can't comment on conflicts or compatibility in the future, I just described a feature that would be very useful to my users who constantly complain about page damage.

deekerman commented

2026-03-04 01:06:05 -05:00

Author

Owner

@ghost commented on GitHub (Dec 10, 2019):

✌

@ghost commented on GitHub (Dec 10, 2019): ✌

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#1146

No description provided.

Rows
Columns