mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 09:25:56 +03:00
[GH-ISSUE #426] The port 53 is already used on windows by some other services #149
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#149
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 @HomeOfTheWizard on GitHub (Aug 25, 2023).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/426
Hi,
I am on windows 10 Family v 22h2
docker desktop 4.21.1
DSP version 3.16.0
https://github.com/mageddo/dns-proxy-server/releases/tag/3.16.0-snapshot
I cannot launch the app via docker or via executable manually.
It is because the port 53 is already in use by some windows services
https://superuser.com/questions/1633432/why-windows-10-has-a-svchost-process-that-listen-on-port-53
https://answers.microsoft.com/en-us/windows/forum/all/solved-unable-to-stop-internet-connection-sharing/b01e1ebc-4f9d-4bf6-8d15-37a782fa03ff
I cant turn off this service cause it is used by HyperV, so I cannot launch docker if I turn it off.
@HomeOfTheWizard commented on GitHub (Aug 25, 2023):
here are the logs for the docker run
@HomeOfTheWizard commented on GitHub (Aug 25, 2023):
Here are the logs for the executable's run
@kassi commented on GitHub (Oct 23, 2023):
Same on MacOS, trying to run the docker service.
@mageddo commented on GitHub (Apr 23, 2024):
Hey, it's really troublesome because Windows hasn't an option to specify a custom port, what you can do is try like @kassi said and run DPS inside a container pointing windows to the to the container IP instead.
@mageddo commented on GitHub (May 29, 2024):
Closing this issue, feel free to reopen it when you are able to respond