mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Configuration of a reverse proxy to one AdGuardHome instance with different block lists #3476
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#3476
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @c-key on GitHub (Feb 11, 2022).
Prerequisites
Problem Description
Is there a way to configure different reverse proxy urls to one AdGuardHome instance with different block lists?
One example maybe for a better understanding.
I configure a reverse proxy url named .../tracking-filter-doh/..., this route will be used to block only tracking lists. Another reverse proxy url named .../ad-filter-doh/... will be used to block tracking and ads. Both reverse proxy urls will be redirect to one local AdGuardHome running instance.
Is there a way to configure this behaviour? Maybe with special settings (headers or something else) in the reverse proxy url configuration which redirect to AdGuardHome?
Proposed Solution
I think one way to do this is, to run multiple instance of AdGuardHome in which are different lists of blocking types like tracking and/or ads.
Alternatives Considered
But maybe it is possible to configure a header or something else to use only selected block lists of the one local running AdGuardHome instance. Something like ctag or clientip differentiation.
Additional Information
@ainar-g commented on GitHub (Feb 11, 2022):
Hello. In v0.108.0 we are going to add the feature of having different filtering lists for different clients; see #435. That, along with ClientIDs would allow you to use different URLs to get different types of filtering. Would that work for you?
@c-key commented on GitHub (Feb 19, 2022):
Thanks for your answer. It looks like what I am looking for. I will wait for v0.108.0 and test ist.