AdguardTeam/AdGuardHome

AdGuard Home's DNS-over-TLS port 853 is not working

Open

#4,963 opened on Sep 28, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (2,333 forks)batch import
help wantedwaiting for data

Repository metrics

Stars
 (34,000 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to report a bug and not ask a question

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

x86

Installation

Snapcraft

Setup

On one machine

AdGuard Home version

v0.107.13

Description

I am using RHEL-8.6.0 system in aws ec2, I have configured ssl certificate, ec2 security group has squared port 853. Port 853 is not working, I check that port 853 is listening, no firewall is enabled, but port 853 is always in filtered state. I use nmap to scan 127.0.0.1 and find that port 853 is in open state, but when I use nmap to scan public ip, I find that it is in filtered state. Is this a problem caused by incompatibility with RHEL-8.6.0? Sorry, I forgot to mention

Contributor guide

Research direction
Check if port 853 is blocked by external firewall, SELinux, or cloud security group; verify DNS over TLS configuration.
Tech stack
go
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Basic networkingDNS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70