-
Notifications
You must be signed in to change notification settings - Fork 11.2k
-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
修复Failed to start: app/proxyman/inbound: failed to listen TCP on 10808 > transport/internet: failed to listen on address问题 #1735
Comments
绑定端口没权限,我猜是hyper-v的锅,在启用了wsl2 或者windows sandbox 的情况下会出现。或者端口被占用? |
netstat -aon|findstr "10808" |
我遇到了同样的问题,执行 |
我在使用CTRL+R测试连接时也遇到了同样的问题,但是不影响对网络的访问,本地监听端口为默认的10808,log信息为:
PowerShell 运行结果: ➜ netstat -aon|findstr "10808" |
选中多个测试真连接延迟会开启多个进程占用端口, 如果其中有一个无法绑定端口就会报错 @younger-1 |
@symant233 现在没有问题了,不知道是因为更新了服务器链接还是重启了机器 |
我也遇到了同樣的問題。把10808端口改成其他5位數的不行,改成4位數1080就可以了。但查看了端口占用和防火墻,沒有10808等端口被占用啊。 |
hy-v 虚拟机会自动分配端口,每次打开都不一样,有一台好就是恰好端口没有占用到。 设置系统动态端口的范围,指定系统的动态端口是从50000 开始 数量为 10000 个,重启以后一般就OK了。 |
碰到了同样的问题 |
|
感谢~ |
Xray 1.5.4 (Xray, Penetrates Everything.) Custom (go1.17.7 windows/386) 请问在这个怎么解决?谢谢各位大神 |
You should run v2ray app as an administrator. |
设置里,参数设置换个端口能解决。具体原因不清楚 |
guys I had this problem , even download another version but didn't work. |
端口改成 4位就可以了。也不知道为啥? |
好像是测试时会占用很多端口,端口冲突。重启电脑或者换个不会冲突的端口可以解决 |
我出现刚问题的原因是因为开启hyper-V出现的,原因是开启Hyper-V后,系统默认会分配给一些保留端口供Hyper-V使用: |
|
tks! this is the easy way to do it! |
我也遇到了这个问题,也是绑定失败,找不到占用端口的进程 在网上搜到的解决方案是:
(来源:简书) |
我情况就是这样,这个命令真的节省了我很多时间!感谢你! |
更新到最新版也还是没用,求修复下
启动服务(2021/8/11 18:35:45)...
2021/08/11 18:35:45 Using default config: D:\v2rayN\config.json
Xray 1.4.2 (Xray, Penetrates Everything.) Custom (go1.16.2 windows/amd64)
A unified platform for anti-censorship.
2021/08/11 18:35:45 [Info] infra/conf/serial: Reading config: D:\v2rayN\config.json
Failed to start: app/proxyman/inbound: failed to listen TCP on 10808 > transport/internet: failed to listen on address: 127.0.0.1:10808 > transport/internet/tcp: failed to listen TCP on 127.0.0.1:10808 > listen tcp 127.0.0.1:10808: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
The text was updated successfully, but these errors were encountered: