mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Accidently banned Lark #1461
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#1461
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 @kmahyyg on GitHub (Apr 10, 2020).
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details
v0.101.0
Deployed on my Laptop currently used to send this issue out.
Windows 10 1909
Expected Behavior
Working Properly when trying to load Lark Cloud Documents.
Actual Behavior
Get banned.
Additional Information
As #950 introduced the ban to TikTok. The online conferencing software made by the same company which named as "Lark" was also get banned. Lark is using the same domain for users' documents, it get accidentally banned by the TikTok rules.
According to captured data from TLS SNI, the following domain names should be whitelisted:
*.byteoversea.com( currently maliva-mcs.byteoversea.com vaali-mcs.byteoversea.com, mon-va.byteoversea.com)*.larksuite.com*.larksuitecdn.com@ameshkov commented on GitHub (Apr 13, 2020):
Hm, but according to your log it's not blocked. It's your DNS server that returns NXDOMAIN for it, AGH just shows you the information on the domain that we have.
@kmahyyg commented on GitHub (Apr 13, 2020):
Then why I use kdig to tls://1.1.1.1 and get correct answer? this is the problem.
@ameshkov commented on GitHub (Apr 13, 2020):
To troubleshoot this issue we need to see AdGuard Home logs.
log_fileverbosetoTrue@hnnweb commented on GitHub (Apr 14, 2020):
In the first picture
Please hover your mouse over the right questionmark to find out which filter that is blocking.
The "Found in the known domains database" is just information about the domainname.
@kmahyyg commented on GitHub (Apr 15, 2020):
Log File attached here:
logfile-20200416.log
@hnnweb commented on GitHub (Apr 16, 2020):
Just by going to their homepage and clicking "Let's get started" triggers "s16.bytesoverseas.com". Atleast for me.
This is what i see in my Console
@kmahyyg commented on GitHub (Apr 16, 2020):
Okay, it's not your problem. But the rules problem. AdGuard Simplified Domain Names filter, this blocklist is the killer. I'll manually whitelist the whole domain I need.
@kmahyyg commented on GitHub (Apr 16, 2020):
By the way, I use their client software. Not Web.
@ameshkov commented on GitHub (Apr 17, 2020):
@kmahyyg ah, so blocking
byteoversea.comis the root cause, we'll unblock it, thank you!@Alex-302 commented on GitHub (Apr 17, 2020):
Removed recenly added rule:
||byteoversea.com^