You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
Description
my question
I hope that adguardhome can add an http or socks5 proxy function to solve the problem that some countries and regions cannot parse ad filtering rules and private dns.
In China, adguardhome cannot parse most private dns because its port 853 has been blocked (the Great Firewall of China)
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
Description
my question
I hope that adguardhome can add an http or socks5 proxy function to solve the problem that some countries and regions cannot parse ad filtering rules and private dns.
In China, adguardhome cannot parse most private dns because its port 853 has been blocked (the Great Firewall of China)
I use Adguard Home in China, and it works smoothly. I don't think proxy/sock5 is even necessary because we all use passwall/bypass which can easily update all filters.
And for private DNS, I use nextdns with cloudflare worker. The link you shared, mentioned that cloudflare worker doesn't' work, but I can easily use it. I setup it with this script https://github.com/tina-hello/doh-cf-workers
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
Description
my question
I hope that adguardhome can add an http or socks5 proxy function to solve the problem that some countries and regions cannot parse ad filtering rules and private dns.
In China, adguardhome cannot parse most private dns because its port 853 has been blocked (the Great Firewall of China)
Details
https://bangumi.tv/group/topic/369549
net4people/bbs#68 (comment)
The text was updated successfully, but these errors were encountered: