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

"Ports are not available: exposing port UDP ... forbidden by its access permissions." (can't start neko with Quick Start) #435

Open
Daoet opened this issue Oct 19, 2024 · 3 comments
Labels
not our bug Bug is inside used dependency / library

Comments

@Daoet
Copy link

Daoet commented Oct 19, 2024

I can't start neko going through the Quick Start guide.

Using the commands docker compose up -d or docker compose up or starting it in Docker Desktop, I get output similar to this:

in Docker Desktop

`Cannot start Docker Compose application. Reason: compose [start] exit status 1. Container 1bu-neko-1 Starting Error response from daemon: Ports are not available: exposing port UDP 0.0.0.0:52009 -> 0.0.0.0:0: listen udp 0.0.0.0:52009: bind: An attempt was made to access a socket in a way forbidden by its access permissions.`

docker compose up -d

D:\1bu>docker compose up -d
time="2024-10-19T15:49:45+02:00" level=warning msg="D:\\1bu\\docker-compose.yaml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
[+] Running 0/0
 - Container 1bu-neko-1  Starting                                                                                                                                                      0.0s
Error response from daemon: Ports are not available: exposing port UDP 0.0.0.0:52032 -> 0.0.0.0:0: listen udp 0.0.0.0:52032: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
  • I've done router port forwarding for udp: Public Ports 52000:52100 (Private Ports are of the same range)
  • I've also done router port forwarding for tcp 8090, but idk if that's necessary.
  • I've have first omitted NEKO_NAT1TO1: , and later included NEKO_NAT1TO1: {IP_address} with my device's private IP address to the docker-compose.yaml from the link in Quick Start guide.

some other info:

  • OS: Windows 10 Home V 22H2
  • docker image: m1k1o/neko:firefox

Can someone help me out?

@m1k1o
Copy link
Owner

m1k1o commented Oct 19, 2024

Neko was created and tested on linux (debian based distros) therefore I cannot help you with Windows.

If udp is not working on Windows just try to expose tcp port of TCPMUX. It is not solving the issue, but rather that workaround if UDP ports are the issue.

@Daoet
Copy link
Author

Daoet commented Oct 21, 2024

Using TCPMUX fixes the issue of neko not being able to run. (https://neko.m1k1o.net/#/getting-started/?id=using-mux-instead-of-epr)

As for Windows, I can try to install Docker and run neko it on the Ubuntu distro later (through WSL; Windows Subsystem for Linux).
But before I do that (and uninstall Docker Desktop for Windows), would it be okay to send you neko's debug log to see why certain connections fails?
Because I'm not sure whether the next problem (of not being able to connect at all externally, and internally connection and use being limited to my host machine only) has to do with Windows, the configuration of neko, or whether it is exclusive to networking itself.
If yes, I'll make a new github issue for this and share the debug log there, along with additional info I found when trying to troubleshoot it myself.

Also regarding the debug log, would you prefer me to upload the whole debug log, or just the relevant info? What relevant info would you require, and what 'sensitive information' (if any) would you suggest leaving out when sharing the debug log?

@m1k1o
Copy link
Owner

m1k1o commented Nov 7, 2024

You can sumarize your findings regarding problems on windows here, the more verbose the better. But since I only use linux I cannot take a look into it. But it might help other people who are also trying to run this under Windows.

@m1k1o m1k1o added the not our bug Bug is inside used dependency / library label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not our bug Bug is inside used dependency / library
Projects
None yet
Development

No branches or pull requests

2 participants