AdguardTeam / AdGuardHome

Network-wide ads & trackers blocking DNS server
https://adguard.com/adguard-home/overview.html
GNU General Public License v3.0
25.74k stars 1.85k forks source link

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

Open SuAdnim opened 2 years ago

SuAdnim commented 2 years ago

Prerequisites

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

ishanjain28 commented 2 years ago

@SuAdnim Is the ec2 security group configured to allow incoming traffic on port 853?

ghost commented 7 months ago

Hi @SuAdnim, are you still experiencing this with the latest version of AdGuard Home?

iAmBipinPaul commented 2 months ago

I'm rerunning behind reverser proxy traefik and I get this error

traefik-1    | time="2024-09-14T15:25:03Z" level=error msg="Error while connecting to backend: dial tcp 172.19.0.3:853: connect: connection refused"

DNS over https work fine