[GH-ISSUE #2417] [W] [control.go:121] login to server failed: broken pipe #1922

New issue

Closed

opened 2026-05-05 13:14:20 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 13:14:20 -06:00

Owner

Originally created by @276562578 on GitHub (May 29, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2417

一直提示broken pipe
之前一直用着挺好的，然后也能从客户端连接到服务端，telnet端口也是可以打开的，关于网络问题用了ping来测试，也问题不大，唯一异常一点的就是telnet打开端口会有一点慢，但一定能打开
尝试用kcp，不能解决
--- 219.217.54.128 ping statistics ---
65084 packets transmitted, 65083 received, 0.00153648% packet loss, time 60450ms
rtt min/avg/max/mdev = 0.604/0.885/14.843/0.380 ms, pipe 2, ipg/ewma 0.928/0.845 ms

[REQUIRED] hat version of frp are you using

Version:0.14.1

[REQUIRED] What operating system and processor architecture are you using
OS:Linux
CPU architecture:

[REQUIRED] description of errors

confile

client
[common]
server_addr =
server_port =
privilege_token =
login_fail_exit = false
#kcp_bind_port = 17010
#protocol = kcp

[seafile]
type = tcp
local_ip = 127.0.0.1
local_port = 8008
remote_port = 18008

server
[common]
bind_port = 17009
privilege_token = 111
#kcp_bind_port = 17010

log file

client
2021/05/29 09:31:19 [W] [control.go:121] login to server failed: broken pipe
2021/05/29 09:31:49 [W] [control.go:121] login to server failed: broken pipe
server
2021/05/29 09:31:19 [W] [service.go:239] Accept new mux stream error: broken pipe
2021/05/29 09:31:49 [W] [service.go:239] Accept new mux stream error: broken pipe

Originally created by @276562578 on GitHub (May 29, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2417 一直提示broken pipe 之前一直用着挺好的，然后也能从客户端连接到服务端，telnet端口也是可以打开的，关于网络问题用了ping来测试，也问题不大，唯一异常一点的就是telnet打开端口会有一点慢，但一定能打开尝试用kcp，不能解决 --- 219.217.54.128 ping statistics --- 65084 packets transmitted, 65083 received, 0.00153648% packet loss, time 60450ms rtt min/avg/max/mdev = 0.604/0.885/14.843/0.380 ms, pipe 2, ipg/ewma 0.928/0.845 ms **[REQUIRED] hat version of frp are you using**  Version:0.14.1 **[REQUIRED] What operating system and processor architecture are you using** OS:Linux CPU architecture: **[REQUIRED] description of errors** **confile**  client [common] server_addr = server_port = privilege_token = login_fail_exit = false #kcp_bind_port = 17010 #protocol = kcp [seafile] type = tcp local_ip = 127.0.0.1 local_port = 8008 remote_port = 18008 server [common] bind_port = 17009 privilege_token = 111 #kcp_bind_port = 17010 **log file**  client 2021/05/29 09:31:19 [W] [control.go:121] login to server failed: broken pipe 2021/05/29 09:31:49 [W] [control.go:121] login to server failed: broken pipe server 2021/05/29 09:31:19 [W] [service.go:239] Accept new mux stream error: broken pipe 2021/05/29 09:31:49 [W] [service.go:239] Accept new mux stream error: broken pipe

gitea-mirror

2026-05-05 13:14:20 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:14:23 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 14, 2021):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jul 14, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.