github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #697] [control.go:109] login to server failed: broken pipe. #547

New issue

Closed

opened 2026-05-05 12:21:26 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

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

Owner

Originally created by @nyhpro on GitHub (Apr 9, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/697

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。)

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?
0.16.1 Frps and Frpc

What operating system and processor architecture are you using (go env)?
CentOS 7 Go env

Configures you used:
The alarm information is [control.go:109] login to server failed: broken pipe.
Frps:
You Server IP : 35.201.150.123
Bind port : 5443
kcp support : false
vhost http port : 80
vhost https port : 443
Dashboard port : 6443
Dashboard user : admin
Dashboard password : 123456
Privilege token : 123456
tcp_mux : false
Max Pool count : 50
Log level : info
Log max days : 3
Log file : enable

Frpc:
[common]
server_addr = 35.201.150.123
server_port = 5443
privilege_token = 123456

Steps to reproduce the issue:

all the setting has been settled on Frps and I can visit by web dash board by IP:6443, no firewall setting blocked. The time zone have been set aligned on the server and client.
Frpc setting is basic and sample.
I run Frpc.exe -c frpc.ini on windows and got the alarm: [control.go:109] login to server failed: broken pipe.

Describe the results you received:
[control.go:109] login to server failed: broken pipe.

Describe the results you expected:
I want to know what's broken pipe's meaning and how to deal with it.

Additional information you deem important (e.g. issue happens only occasionally):
If possible, is there any more informatio about alarm or error for user, thanks.
Can you point out what caused this issue (optional)
No idea, I installed FRPS on two different VPS, When I use the Frpc on my windows, Same alarm information on the Frpc. I installed Frpc on router and windows, same alarm information.

Originally created by @nyhpro on GitHub (Apr 9, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/697 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。) Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** 0.16.1 Frps and Frpc **What operating system and processor architecture are you using (`go env`)?** CentOS 7 Go env **Configures you used:** The alarm information is [control.go:109] login to server failed: broken pipe. Frps: You Server IP : 35.201.150.123 Bind port : 5443 kcp support : false vhost http port : 80 vhost https port : 443 Dashboard port : 6443 Dashboard user : admin Dashboard password : 123456 Privilege token : 123456 tcp_mux : false Max Pool count : 50 Log level : info Log max days : 3 Log file : enable Frpc: [common] server_addr = 35.201.150.123 server_port = 5443 privilege_token = 123456 **Steps to reproduce the issue:** 1. all the setting has been settled on Frps and I can visit by web dash board by IP:6443, no firewall setting blocked. The time zone have been set aligned on the server and client. 2. Frpc setting is basic and sample. 3. I run Frpc.exe -c frpc.ini on windows and got the alarm: [control.go:109] login to server failed: broken pipe. **Describe the results you received:** [control.go:109] login to server failed: broken pipe. **Describe the results you expected:** I want to know what's broken pipe's meaning and how to deal with it. **Additional information you deem important (e.g. issue happens only occasionally):** If possible, is there any more informatio about alarm or error for user, thanks. **Can you point out what caused this issue (optional)** No idea, I installed FRPS on two different VPS, When I use the Frpc on my windows, Same alarm information on the Frpc. I installed Frpc on router and windows, same alarm information.

gitea-mirror

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

closed this issue
added the
WaitingForInfo
label

gitea-mirror commented

2026-05-05 12:21:29 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 9, 2018):

No useful info, maybe it's a network error.

@fatedier commented on GitHub (Apr 9, 2018): No useful info, maybe it's a network error.

gitea-mirror commented

2026-05-05 12:21:30 -06:00

Author

Owner

@nyhpro commented on GitHub (Apr 13, 2018):

I used xfrp instead of frp on the same VPS, same configuration, it is worked. It looks like is FRPS's problem on broken pipe. Fatedier,can you have a look on the program?

@nyhpro commented on GitHub (Apr 13, 2018): I used xfrp instead of frp on the same VPS, same configuration, it is worked. It looks like is FRPS's problem on broken pipe. Fatedier,can you have a look on the program?

gitea-mirror commented

2026-05-05 12:21:31 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 19, 2018):

Sorry, i won't do that. If you find more useful information, reopen this issue.

@fatedier commented on GitHub (Apr 19, 2018): Sorry, i won't do that. If you find more useful information, reopen this issue.

gitea-mirror commented

2026-05-05 12:21:33 -06:00

Author

Owner

@KitGavinx commented on GitHub (Jul 29, 2018):

我也遇到了这个问题，不过后来解决了，客户端和服务端最好用同一个版本。配置按照frpc_full.ini的写就可以了

@KitGavinx commented on GitHub (Jul 29, 2018): 我也遇到了这个问题，不过后来解决了，客户端和服务端最好用同一个版本。配置按照frpc_full.ini的写就可以了

gitea-mirror commented

2026-05-05 12:21:33 -06:00

Author

Owner

@599316527 commented on GitHub (Oct 27, 2018):

@KitGavinx 感谢！我也碰到了这个问题，百思不得其解，看了你的回复受到了启发。我服务器迁移后下载了最新的 frp，但是本地电脑上还是旧版的，两边版本不一致导致连不上。

For english speaker: Make sure both frps and frpc are the same version.

@599316527 commented on GitHub (Oct 27, 2018): @KitGavinx 感谢！我也碰到了这个问题，百思不得其解，看了你的回复受到了启发。我服务器迁移后下载了最新的 frp，但是本地电脑上还是旧版的，两边版本不一致导致连不上。 For english speaker: Make sure both frps and frpc are the same version.

gitea-mirror commented

2026-05-05 12:21:34 -06:00

Author

Owner

@hz0ne commented on GitHub (Feb 13, 2020):

相同版本的frp，仍然出现过这种问题导致断开，两边的日志都看不到错误出现，重连能够成功

@hz0ne commented on GitHub (Feb 13, 2020): 相同版本的frp，仍然出现过这种问题导致断开，两边的日志都看不到错误出现，重连能够成功