[Resolved] messenger.com [Windows] Blank

[Bushido]

The messenger.com website is blank if Adguard Assistant is enabled. After disabling filtering on messenger.com via Assistant, then messenger.com webpage appears.
With Adguard filtering:
Without Adguard filtering:

Direct link to the website: https://www.messenger.com
List of filters enabled on your device:
Using products: Adguard for Windows latest beta, Assistant

 

[Alex302]

Please check this rule:

@@||messenger.com^$extension

 

[Bushido]

@Alex302 Thank you! It worked.

 

[Alex302]

Ok, added.

 

[Bushido]

@Alex302 The issue has returned. This time the Assistant icon does not appear too.
If I disable AdGuard Base Filter, then I get a white page with Assistant icon.
If I disable User Filter, I can use the page as normal.
If I search the rule "messenger.com" in User Filter, then I get no hits.
How to detect which rule of User Filter breaks messenger.com if the domain "messenger.com" is not causing it?

 

[Blaz]

You can check filtering log to see if a url block rule is applied there. Alternatively you can disable rules in user filter manually until you hit the correct one.

 

[Bushido]

You can check filtering log to see if a url block rule is applied there. Alternatively you can disable rules in user filter manually until you hit the correct one.

I am attaching the filtering log.

 

[Blaz]

Looks like some kind of generic rule.

Try to search your user filter for "##" (without "). It is normal the assistant is not showing up due to exclusion rule in Base filter.
You can try this rule in your user filter to disable generichide rules and disable Assistant:

@@||messenger.com^$generichide,extension,important

 

[Bushido]

Looks like some kind of generic rule.

Try to search your user filter for "##" (without "). It is normal the assistant is not showing up due to exclusion rule in Base filter.
You can try this rule in your user filter to disable generichide rules and disable Assistant:

@@||messenger.com^$generichide,extension,important

This ruled fixed the problem. Thank you!
How to detect the problematic generic rule?

 

[Blaz]

You search for ## in user filter and disable several of them (those which do not have any domain in front of them or have ~domain.com##) until you find the correct one.