[BUG] Isolated clients (Use global settings disabled) cannot be targeted by Custom Rules or tested in Check Filtration

[masterwishx]

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 or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

Docker

Setup

On one machine

AdGuard Home version

v0.107.78

Action

Description of the Problem

When editing a specific client (e.g., Kevin_PC-Lan), if you disable the "Use global settings" toggle to isolate the client, it completely removes the client's ability to interact with the main "Custom Filtering Rules" page.

This creates two critical issues:

1. Check Filtration tool becomes useless for this client:
   If I try to test a domain using the "Check Filtration" (Проверить фильтрацию) utility and enter this specific ClientID/IP, the tool completely ignores any blocking rules and falsely outputs: "Not found in your filters list". It seems the backend engine immediately drops the query simulation before evaluating custom syntax because of the global settings flag.

2. No way to apply individual custom domains:
   Since the text input box for individual client rules was removed from the Client UI in recent updates, and the client now completely bypasses the global "Custom Filtering Rules" list, there is no way to block a specific custom domain (e.g., a private domain like upgrader.pro) exclusively for this client using standard syntax like ||domain.com^$client='Client_Name'.

Expected Behavior

• The "Check Filtration" tool should accurately simulate and display hits on rules matching the $client modifier, even if that client has "Use global settings" turned off.
• There should be a clear, documented path to apply individual custom domain block/allow rules to an isolated client without forcing them to inherit the entire global blocklist environment.

Actual Behavior

The custom rules with $client='Client_Name' or $client=IP are completely ignored by the engine and the testing tool if "Use global settings" is turned off for that client.

# Kevin PC Blocked
||pornhub.com^$client='Kevin_PC-Lan'
||upgrader.pro^$client='Kevin_PC-Lan'
||upgrader.pro^$important,client='192.168.0.101'

Replace the following command with the one you're calling or a
description of the failing action:

nslookup -debug -type=a upgrader.pro 192.168.0.198
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 1, rcode = NXDOMAIN
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        198.0.168.192.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  198.0.168.192.in-addr.arpa
        ttl = 10 (10 secs)
        primary name server = fake-for-negative-caching.adguard.com
        responsible mail addr = hostmaster.198.0.168.192.in-addr.arpa
        serial  = 100500
        refresh = 1800 (30 mins)
        retry   = 900 (15 mins)
        expire  = 604800 (7 days)
        default TTL = 86400 (1 day)

------------
╤хЁтхЁ:  UnKnown
Address:  192.168.0.198

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
        upgrader.pro, type = A, class = IN
    ANSWERS:
    ->  upgrader.pro
        internet address = 45.199.188.12
        ttl = 171 (2 mins 51 secs)

------------
Не заслуживающий доверия ответ:
╚ь :     upgrader.pro
Address:  45.199.188.12

Expected result

check filter and custom filter should work for client with disabled global config

Actual result

check filter and custom filter not working for client with disabled global config

Additional information and/or screenshots

No response

[masterwishx]

closed opened before discussion #8476 as it seems more like bug to me ...

[masterwishx]

Sorry my bad was need to enable this option for it :

[masterwishx]

Well ,if i enable block host with filters ,its basicly same as enable global settings with filters ?

[masterwishx]

The only way I found is:

1.enable filters or global for client.
2. Add custom rule for allow all to client
3. Then block with important custom rule

Maybe any easy way avaliable, or this is the only way?

[Dynamic5912]

Too much going on here over multiple posts.

What exactly is the issue?

[masterwishx]

Too much going on here over multiple posts.

What exactly is the issue?

Yep, sorry for this.
I wanted to block some sites for user that had :
Use global settings =off, use filters=off

So found, I can't set custom rules until user has option (use global settings=on or use filters=on).

So I need to enable for user:

1. enable filters or global for client.
2. Add custom rule for allow all to client
3. Then block with important custom rule

# Kevin PC Blocked
@@||*^$client='Kevin_PC-Lan'
||pornhub.com^$important,client='Kevin_PC-Lan'
||upgrader.pro^$important,client='Kevin_PC-Lan'

This is logical correct (if client not has option filters enabled = not using filters) but not documented I think and took a lot of time to understand how to set it.
Also I saw we have some pr #8274 for get to client separate filter lists ...

For now it was fixed , can be moved to disscusion maybe?