mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
listen tcp :53: protocol not available #412
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#412
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @apeng2012 on GitHub (Nov 23, 2018).
Actual behavior
Screenshot:
Your environment
@hmage commented on GitHub (Nov 23, 2018):
Hi.
What Linux distribution are you using? Debian? Ubuntu? Do you have any linux kernel security installed and activated like SElinux, AppArmor, GrSecurity, SecComp or something similar?
@apeng2012 commented on GitHub (Nov 23, 2018):
Linux openmediavault 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 x86_64
openmediavault is the next generation network attached storage (NAS) solution based on Debian Linux.
@ghost commented on GitHub (Dec 21, 2018):
Sudo systemctl disable system-resolved
Restart then try again
@apeng2012 commented on GitHub (Dec 24, 2018):
p.s. The system has two network cards, bridged
@ameshkov commented on GitHub (Dec 25, 2018):
@apeng2012 could you please try building AG from the master branch? There were some massive changes lately and it might help
@be2clack commented on GitHub (Feb 1, 2019):
I also have such a problem? Ubuntu! how to solve ??????
@ultimatevn commented on GitHub (Mar 8, 2019):
Im using Debian 9 and cant install AdGuardHome, it's said
Port 53 is not available for binding -- this will make DNS clients unable to contact AdGuard Home.
What i do...
@Who-42 commented on GitHub (Mar 8, 2019):
systemctl disable systemd-resolved.service
service systemd-resolved stop
solves your problem @ultimatevn
@ultimatevn commented on GitHub (Mar 8, 2019):
@CWo42 not working :(
@Who-42 commented on GitHub (Mar 8, 2019):
strange on my debian that was working
can you eval whats using 53?
@ultimatevn commented on GitHub (Mar 8, 2019):
@CWo42 I dont know what application use port 53, i dont see that port in netstat
@ameshkov commented on GitHub (Mar 9, 2019):
@ultimatevn what exact error do you see in the AGH console output?
Are you running AGH under root?
@ultimatevn commented on GitHub (Mar 13, 2019):
Already run on root privilege...
On Sat, Mar 9, 2019, 21:47 Andrey Meshkov notifications@github.com wrote:
@ameshkov commented on GitHub (Mar 14, 2019):
@ultimatevn could you please share your AdGuardHome.yaml?
Try changing DNS interface from 0.0.0.0 to 127.0.0.1 for instance.
@apeng2012 commented on GitHub (May 26, 2019):
v0.95-hotfix can run