[GH-ISSUE #1594] windows版本frpc，使用stcp协议，无法在0.0.0.0开端口 #1262

New issue

Closed

opened 2026-05-05 12:48:22 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 12:48:22 -06:00

Owner

Originally created by @jasonto87 on GitHub (Jan 6, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/1594

windows版本frpc，使用stcp协议，无法在0.0.0.0开端口。只能够通过localhost:port访问，无法通过ip:port访问 netstat看到监听只能开在127.0.0.1

Originally created by @jasonto87 on GitHub (Jan 6, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/1594 windows版本frpc，使用stcp协议，无法在0.0.0.0开端口。只能够通过localhost:port访问，无法通过ip:port访问 netstat看到监听只能开在127.0.0.1

gitea-mirror closed this issue

2026-05-05 12:48:23 -06:00

gitea-mirror commented

2026-05-05 12:48:25 -06:00

Author

Owner

@QQ2017 commented on GitHub (Jan 6, 2020):

私密代理客户端A
local_ip = 192.168.100.100
local_port = 22

私密代理客户端B(查看端)
bind_addr = 0.0.0.0
bind_port = 2222

测试私密代理客户端B是可以监听0.0.0.0:2222，并且访问2222能连上私密代理客户端A的指定的192.168.100.100:22
所以你是不是搞错？

@QQ2017 commented on GitHub (Jan 6, 2020): **私密代理客户端A** local_ip = 192.168.100.100 local_port = 22 **私密代理客户端B(查看端)** bind_addr = 0.0.0.0 bind_port = 2222 测试私密代理客户端B是可以监听0.0.0.0:2222，并且访问2222能连上私密代理客户端A的指定的192.168.100.100:22 所以你是不是搞错？

gitea-mirror commented

2026-05-05 12:48:25 -06:00

Author

Owner

@jasonto87 commented on GitHub (Jan 6, 2020):

确实没有，用开启了加密和tls,在客户端B这里，netstat -ano|findstr "2222" 只有127.0.01:2222在listen

@jasonto87 commented on GitHub (Jan 6, 2020): 确实没有，用开启了加密和tls,在客户端B这里，netstat -ano|findstr "2222" 只有127.0.01:2222在listen

gitea-mirror commented

2026-05-05 12:48:26 -06:00

Author

Owner

@jasonto87 commented on GitHub (Jan 6, 2020):

补充一下。这个问题在linux上不存在，使用sudo权限启动frpc即能在0.0.0.0上监听。但是win7下只能在127.0.0.1上监听

@jasonto87 commented on GitHub (Jan 6, 2020): 补充一下。这个问题在linux上不存在，使用sudo权限启动frpc即能在0.0.0.0上监听。但是win7下只能在127.0.0.1上监听

gitea-mirror commented

2026-05-05 12:48:27 -06:00

Author

Owner

@QQ2017 commented on GitHub (Jan 7, 2020):