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
Many thanks to all contributors to this great project
What problem are you trying to solve?
the Adguard main Page should not be accessible from the outside.
Preface:
Some of my end-clients (friends) want to switch to using DoH. They were previously using DoT, where requests reached the server on Port 853, and NginX blocked communication with the AdGuardServer on any other ports.
//// >> I accessed the AdGuard Console by using a VPN tunnel through example.net on Port 443.
The problem:
If I redirect the subdomain dns.example.net/dns-query to the AdGuard Server using NginX, the console will become publicly accessible, allowing anyone to test their skills on my implementation.
Proposed solution:
Is it possible to restrict access to the AdGuard Login Page only to the domain <example.net>? I want to prevent traffic from IPs other than my VPN from accessing the domain.
In this case, AdGuard will only accept logins through example.net, while allowing DoH requests from all other domains or subdomains pointing to the server.
The text was updated successfully, but these errors were encountered:
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
Many thanks to all contributors to this great project
What problem are you trying to solve?
the Adguard main Page should not be accessible from the outside.
Preface:
Some of my end-clients (friends) want to switch to using DoH. They were previously using DoT, where requests reached the server on Port 853, and NginX blocked communication with the AdGuardServer on any other ports.
//// >> I accessed the AdGuard Console by using a VPN tunnel through example.net on Port 443.
The problem:
If I redirect the subdomain dns.example.net/dns-query to the AdGuard Server using NginX, the console will become publicly accessible, allowing anyone to test their skills on my implementation.
Proposed solution:
Is it possible to restrict access to the AdGuard Login Page only to the domain <example.net>? I want to prevent traffic from IPs other than my VPN from accessing the domain.
In this case, AdGuard will only accept logins through example.net, while allowing DoH requests from all other domains or subdomains pointing to the server.
The text was updated successfully, but these errors were encountered: