[GH-ISSUE #1544] Frpc启动后崩溃，显示Terminated

gitea-mirror commented

2026-05-05 12:46:58 -06:00

Owner

Originally created by @StudentWong on GitHub (Nov 29, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1544

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 将会直接关闭。)
(请不要在 issue 评论中出现无意义的加1，我也是 等内容，将会被直接删除。)
(由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。)

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)?
Both frpc=0.27.1 frps=0.27.1
and
frpc=0.30.0 frps=0.30.0
have been tried

What operating system and processor architecture are you using (go env)?
client

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr/lib/go-1.6"
GOTOOLDIR="/usr/lib/go-1.6/pkg/tool/linux_amd64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"

server

no go env

Configures you used:
frpc.ini

[common]
server_addr = justip
server_port = 235
[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 6000
[web]
type = http
local_port = 8881
custom_domains =justip

frps.ini

[common]
bind_port = 235
vhost_http_port = 8881

Steps to reproduce the issue:
1.Use ssh login and Run frps on CentOS7.3 of Alibaba Cloud
2.Use ssh login Ubuntu 16.04.6 LTS desktop
3.Run frpc on Ubuntu 16.04.6 LTS desktop through ssh

Describe the results you received:
There is no obvious problem with the frps. But the frpc crashs a few seconds after it was started.Sometime it can keep alive until someone login by ssh.

服务端可以正常启动，客户端启动几秒后崩溃，有时可以维持住，但一有穿透的ssh连接，就只能维持几秒。客户端什么错误都不显示，只是终端提示terminated。服务端显示client exit success。

server:

[root@izuf6dkckz53imm18ay4tez frp_0.27.1_linux_amd64]# ./frps -c frps.ini
2019/11/29 18:23:47 [I] [service.go:139] frps tcp listen on 0.0.0.0:235
2019/11/29 18:23:47 [I] [service.go:181] http service listen on 0.0.0.0:8881
2019/11/29 18:23:47 [I] [root.go:204] Start frps success
2019/11/29 18:23:49 [I] [service.go:349] client login info: ip [ip:42325] version [0.27.1] hostname [] os [linux] arch [amd64]
2019/11/29 18:23:49 [I] [http.go:72] [11bb7eb8706c76c7] [web] http proxy listen for host [justip] location []
2019/11/29 18:23:49 [I] [control.go:398] [11bb7eb8706c76c7] new proxy [web] success
2019/11/29 18:23:49 [I] [tcp.go:66] [11bb7eb8706c76c7] [ssh] tcp proxy listen port [6000]
2019/11/29 18:23:49 [I] [control.go:398] [11bb7eb8706c76c7] new proxy [ssh] success
2019/11/29 18:23:56 [I] [control.go:274] [11bb7eb8706c76c7] control writer is closing
2019/11/29 18:23:56 [I] [proxy.go:69] [11bb7eb8706c76c7] [ssh] proxy closing
2019/11/29 18:23:56 [I] [proxy.go:135] [11bb7eb8706c76c7] [ssh] listener is closed
2019/11/29 18:23:56 [I] [proxy.go:69] [11bb7eb8706c76c7] [web] proxy closing
2019/11/29 18:23:56 [I] [control.go:350] [11bb7eb8706c76c7] client exit success

client:

2019/11/29 18:20:33 [I] [service.go:221] login to server success, get run id [b25e0ea6b92fcf04], server udp port [0]
2019/11/29 18:20:33 [I] [proxy_manager.go:137] [b25e0ea6b92fcf04] proxy added: [ssh web]
2019/11/29 18:20:33 [I] [control.go:144] [ssh] start proxy success
2019/11/29 18:20:33 [I] [control.go:144] [web] start proxy success
Terminated

Describe the results you expected:

Frpc not crashing

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Maybe buffer overflow?

Originally created by @StudentWong on GitHub (Nov 29, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1544 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 将会直接关闭。) (请不要在 issue 评论中出现无意义的 **加1**，**我也是** 等内容，将会被直接删除。) (由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。) 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)?** Both frpc=0.27.1 frps=0.27.1 and frpc=0.30.0 frps=0.30.0 have been tried **What operating system and processor architecture are you using (`go env`)?** client >GOARCH="amd64" GOBIN="" GOEXE="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="" GORACE="" GOROOT="/usr/lib/go-1.6" GOTOOLDIR="/usr/lib/go-1.6/pkg/tool/linux_amd64" GO15VENDOREXPERIMENT="1" CC="gcc" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0" CXX="g++" CGO_ENABLED="1" server >no go env **Configures you used:** frpc.ini >[common] server_addr = justip server_port = 235 [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000 [web] type = http local_port = 8881 custom_domains =justip frps.ini >[common] bind_port = 235 vhost_http_port = 8881 **Steps to reproduce the issue:** 1.Use ssh login and Run frps on CentOS7.3 of Alibaba Cloud 2.Use ssh login Ubuntu 16.04.6 LTS desktop 3.Run frpc on Ubuntu 16.04.6 LTS desktop through ssh **Describe the results you received:** There is no obvious problem with the frps. But the frpc crashs a few seconds after it was started.Sometime it can keep alive until someone login by ssh. 服务端可以正常启动，客户端启动几秒后崩溃，有时可以维持住，但一有穿透的ssh连接，就只能维持几秒。客户端什么错误都不显示，只是终端提示terminated。服务端显示client exit success。 server: >[root@izuf6dkckz53imm18ay4tez frp_0.27.1_linux_amd64]# ./frps -c frps.ini 2019/11/29 18:23:47 [I] [service.go:139] frps tcp listen on 0.0.0.0:235 2019/11/29 18:23:47 [I] [service.go:181] http service listen on 0.0.0.0:8881 2019/11/29 18:23:47 [I] [root.go:204] Start frps success 2019/11/29 18:23:49 [I] [service.go:349] client login info: ip [ip:42325] version [0.27.1] hostname [] os [linux] arch [amd64] 2019/11/29 18:23:49 [I] [http.go:72] [11bb7eb8706c76c7] [web] http proxy listen for host [justip] location [] 2019/11/29 18:23:49 [I] [control.go:398] [11bb7eb8706c76c7] new proxy [web] success 2019/11/29 18:23:49 [I] [tcp.go:66] [11bb7eb8706c76c7] [ssh] tcp proxy listen port [6000] 2019/11/29 18:23:49 [I] [control.go:398] [11bb7eb8706c76c7] new proxy [ssh] success 2019/11/29 18:23:56 [I] [control.go:274] [11bb7eb8706c76c7] control writer is closing 2019/11/29 18:23:56 [I] [proxy.go:69] [11bb7eb8706c76c7] [ssh] proxy closing 2019/11/29 18:23:56 [I] [proxy.go:135] [11bb7eb8706c76c7] [ssh] listener is closed 2019/11/29 18:23:56 [I] [proxy.go:69] [11bb7eb8706c76c7] [web] proxy closing 2019/11/29 18:23:56 [I] [control.go:350] [11bb7eb8706c76c7] client exit success client: >2019/11/29 18:20:33 [I] [service.go:221] login to server success, get run id [b25e0ea6b92fcf04], server udp port [0] 2019/11/29 18:20:33 [I] [proxy_manager.go:137] [b25e0ea6b92fcf04] proxy added: [ssh web] 2019/11/29 18:20:33 [I] [control.go:144] [ssh] start proxy success 2019/11/29 18:20:33 [I] [control.go:144] [web] start proxy success Terminated **Describe the results you expected:** >Frpc not crashing **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)** >Maybe buffer overflow?

gitea-mirror closed this issue

2026-05-05 12:46:59 -06:00

gitea-mirror commented

2026-05-05 12:47:01 -06:00

Author

Owner

@deadlineOvO commented on GitHub (Dec 1, 2019):

是不是客户端被连带结束了？
试试用 systemd 服务单元文件看看

@deadlineOvO commented on GitHub (Dec 1, 2019): 是不是客户端被连带结束了？试试用 systemd 服务单元文件看看

gitea-mirror commented

2026-05-05 12:47:02 -06:00

Author

Owner

@fatedier commented on GitHub (Dec 1, 2019):

你需要查看下系统日志为什么进程会被杀掉，frpc 如果正常退出会有一些退出的日志。

@fatedier commented on GitHub (Dec 1, 2019): 你需要查看下系统日志为什么进程会被杀掉，frpc 如果正常退出会有一些退出的日志。

gitea-mirror commented

2026-05-05 12:47:03 -06:00

Author

Owner

@StudentWong commented on GitHub (Dec 2, 2019):

感谢！用自带的服务启动后很稳。

@StudentWong commented on GitHub (Dec 2, 2019): 感谢！用自带的服务启动后很稳。

gitea-mirror commented

2026-05-05 12:47:04 -06:00

Author

Owner

@ray-lee-94 commented on GitHub (May 15, 2020):

感谢！用自带的服务启动后很稳。

能说说具体怎么做吗？求指导

@ray-lee-94 commented on GitHub (May 15, 2020): > 感谢！用自带的服务启动后很稳。能说说具体怎么做吗？求指导

gitea-mirror commented

2026-05-05 12:47:04 -06:00

Author

Owner

@StudentWong commented on GitHub (May 16, 2020):

我是按照这个博客的方法启动的，但是自己创建frps.service没用，把frp_0.XX.X_linux_amd64/systemd/frps.service复制过去就可以了。

https://blog.csdn.net/momo_mutou/article/details/85000056

@StudentWong commented on GitHub (May 16, 2020): 我是按照这个博客的方法启动的，但是自己创建frps.service没用，把frp_0.XX.X_linux_amd64/systemd/frps.service复制过去就可以了。 https://blog.csdn.net/momo_mutou/article/details/85000056

gitea-mirror commented

2026-05-05 12:47:05 -06:00

Author

Owner

@ray-lee-94 commented on GitHub (May 16, 2020):

我的frps是按博客方式启动的,正常启动也很稳定。但是经常断开的是frpc端，同样启动frpc.service无效，启动后很快就terminated

---原始邮件---
发件人: "Student X"<notifications@github.com>
发送时间: 2020年5月16日 11:18:18
收件人: "fatedier/frp"<frp@noreply.github.com>;
抄送: "Comment"<comment@noreply.github.com>;"Li Rui"<945193029@qq.com>;
主题: Re: [fatedier/frp] Frpc启动后崩溃，显示Terminated (#1544)

按照这个博客的方法启动，但是不用自己创建frps.service，把frp_0.XX.X_linux_amd64/systemd/frps.service复制过去就可以了。

https://blog.csdn.net/momo_mutou/article/details/85000056

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ray-lee-94 commented on GitHub (May 16, 2020): 我的frps是按博客方式启动的,正常启动也很稳定。但是经常断开的是frpc端，同样启动frpc.service无效，启动后很快就terminated ---原始邮件--- 发件人: "Student X"<notifications@github.com> 发送时间: 2020年5月16日 11:18:18 收件人: "fatedier/frp"<frp@noreply.github.com>; 抄送: "Comment"<comment@noreply.github.com>;"Li Rui"<945193029@qq.com>; 主题: Re: [fatedier/frp] Frpc启动后崩溃，显示Terminated (#1544) 按照这个博客的方法启动，但是不用自己创建frps.service，把frp_0.XX.X_linux_amd64/systemd/frps.service复制过去就可以了。 https://blog.csdn.net/momo_mutou/article/details/85000056 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

gitea-mirror commented

2026-05-05 12:47:05 -06:00

Author

Owner

@ray-lee-94 commented on GitHub (May 17, 2020):

我的frps是按博客方式启动的,正常启动也很稳定。但是经常断开的是frpc端，同样启动frpc.service无效，启动后很快就terminated
…
---原始邮件--- 发件人: "Student X"<notifications@github.com> 发送时间: 2020年5月16日 11:18:18 收件人: "fatedier/frp"<frp@noreply.github.com>; 抄送: "Comment"<comment@noreply.github.com>;"Li Rui"<945193029@qq.com>; 主题: Re: [fatedier/frp] Frpc启动后崩溃，显示Terminated (#1544) 按照这个博客的方法启动，但是不用自己创建frps.service，把frp_0.XX.X_linux_amd64/systemd/frps.service复制过去就可以了。 https://blog.csdn.net/momo_mutou/article/details/85000056 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

最后应该是客户端ip和其他设备的ip冲突了

@ray-lee-94 commented on GitHub (May 17, 2020): > 我的frps是按博客方式启动的,正常启动也很稳定。但是经常断开的是frpc端，同样启动frpc.service无效，启动后很快就terminated > […](#) > ---原始邮件--- 发件人: "Student X"<notifications@github.com> 发送时间: 2020年5月16日 11:18:18 收件人: "fatedier/frp"<frp@noreply.github.com>; 抄送: "Comment"<comment@noreply.github.com>;"Li Rui"<945193029@qq.com>; 主题: Re: [fatedier/frp] Frpc启动后崩溃，显示Terminated (#1544) 按照这个博客的方法启动，但是不用自己创建frps.service，把frp_0.XX.X_linux_amd64/systemd/frps.service复制过去就可以了。 https://blog.csdn.net/momo_mutou/article/details/85000056 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. 最后应该是客户端ip和其他设备的ip冲突了

Rows
Columns

[GH-ISSUE #1544] Frpc启动后崩溃，显示Terminated #1219