Custom rules don't work #1354

Closed
opened 2026-03-04 01:14:46 -05:00 by deekerman · 5 comments
Owner

Originally created by @lnc1995 on GitHub (Mar 6, 2020).

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

e.g.
tui56.com/ad/

it works on android APP,but doesn't work on router enviroment.
i'm using AdGuardHome_linux_amd64 v0.100.9.

Originally created by @lnc1995 on GitHub (Mar 6, 2020). - [ √] I am running the latest version - [ √] I checked the documentation and found no answer - [ ] I checked to make sure that this issue has not already been filed e.g. tui56.com/ad/ it works on android APP,but doesn't work on router enviroment. i'm using AdGuardHome_linux_amd64 v0.100.9.
Author
Owner

@lnc1995 commented on GitHub (Mar 6, 2020):

I ’m sure other rules are in effect, only my own rules don't work

@lnc1995 commented on GitHub (Mar 6, 2020): I ’m sure other rules are in effect, only my own rules don't work
Author
Owner

@ghost commented on GitHub (Mar 6, 2020):

When add proxy support #391 you'll be able to apply cosmetic rules then follow v0.103 milestone. It may take some time.

@ghost commented on GitHub (Mar 6, 2020): When add proxy support #391 you'll be able to apply cosmetic rules then follow v0.103 milestone. It may take some time.
Author
Owner

@lnc1995 commented on GitHub (Mar 6, 2020):

When add proxy support #391 you'll be able to apply cosmetic rules then follow v0.103 milestone. It may take some time.
Seems doesn't suit my situation.For now, ad blocking is already works.Just some my own rules don't work

@lnc1995 commented on GitHub (Mar 6, 2020): > When add proxy support #391 you'll be able to apply cosmetic rules then follow v0.103 milestone. It may take some time. Seems doesn't suit my situation.For now, ad blocking is already works.Just some my own rules don't work
Author
Owner

@ghost commented on GitHub (Mar 6, 2020):

||.domain.com/ads

Currently adguard home only capable to perform DNS-level blocking, means only domain names. so you have to wait for #391

@ghost commented on GitHub (Mar 6, 2020): `||.domain.com/ads` Currently adguard home only capable to perform DNS-level blocking, means only domain names. so you have to wait for #391
Author
Owner

@lnc1995 commented on GitHub (Mar 7, 2020):

||.domain.com/ads

Currently adguard home only capable to perform DNS-level blocking, means only domain names. so you have to wait for #391

Thanks buddy.I understand what you mean.

@lnc1995 commented on GitHub (Mar 7, 2020): > `||.domain.com/ads` > > Currently adguard home only capable to perform DNS-level blocking, means only domain names. so you have to wait for #391 Thanks buddy.I understand what you mean.
Sign in to join this conversation.
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#1354
No description provided.