Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Site Reachability using a predefined Link #5832

Closed
3 tasks done
ghost opened this issue May 20, 2023 · 1 comment
Closed
3 tasks done

Site Reachability using a predefined Link #5832

ghost opened this issue May 20, 2023 · 1 comment

Comments

@ghost
Copy link

ghost commented May 20, 2023

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.

@ghost
Copy link
Author

ghost commented May 20, 2023

I was able to solve the problem using the following NginX Configuration

location ^~ /login.html { return 404; }
if ($arg_q ~ "^login.html") { return 404; }

it still a nice to have Feature :)

Thanks again

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants