[GH-ISSUE #1602] frpc agent idle settings #1268

New issue

Closed

opened 2026-05-05 12:48:30 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

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

Owner

Originally created by @hehaibo123 on GitHub (Jan 9, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/1602

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)?
./frpc -v0.22.0 ./frps -v0.22.0

What operating system and processor architecture are you using (go env)?
frps:linux-386
frpc:linux-arm

Configures you used:
frps:
[common]
bind_port = 7000
dashboard_port = 7500

dashboard_user = admin
dashboard_pwd = admin

log_file = /data1/frp/frp_0.22.0_linux_386/frp.log
log_level = info
log_max_days = 3

token =

#heartbeat-timeout = 1
tcp_mux = true

authentication_timeout = 0

frpc:
[common]
server_addr =
server_port = 7000

log_file = /usr/HiWoo/frp/frpc.log
log_level = warn
log_max_days = 3

token =

admin_addr = 127.0.0.1
admin_port = 7400

tcp_mux = true

user = 110001912282022001

health_check_type = tcp
health_check_interval_s = 10
health_check_max_failed = 1
health_check_timeout_s = 3

[manager]
type = stcp
sk = 110001912282022001

local_ip = 127.0.0.1
local_port = 9999

use_encryption = true
use_compression = true

Steps to reproduce the issue:
1.Client repeatedly turns off reconnection
2.
3.

Describe the results you received:
Sometimes there are agent idle no connections still online

Describe the results you expected:
Make sure to close the channel offline every time the agent is idle and no connection

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

Can you point out what caused this issue (optional)
Client sands off reconnected agent

Originally created by @hehaibo123 on GitHub (Jan 9, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/1602 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)?** ./frpc -v0.22.0 ./frps -v0.22.0 **What operating system and processor architecture are you using (`go env`)?** frps:linux-386 frpc:linux-arm **Configures you used:** frps: [common] bind_port = 7000 dashboard_port = 7500 dashboard_user = admin dashboard_pwd = admin log_file = /data1/frp/frp_0.22.0_linux_386/frp.log log_level = info log_max_days = 3 token = #heartbeat-timeout = 1 tcp_mux = true authentication_timeout = 0 frpc: [common] server_addr = server_port = 7000 log_file = /usr/HiWoo/frp/frpc.log log_level = warn log_max_days = 3 token = admin_addr = 127.0.0.1 admin_port = 7400 tcp_mux = true user = 110001912282022001 health_check_type = tcp health_check_interval_s = 10 health_check_max_failed = 1 health_check_timeout_s = 3 [manager] type = stcp sk = 110001912282022001 local_ip = 127.0.0.1 local_port = 9999 use_encryption = true use_compression = true **Steps to reproduce the issue:** 1.Client repeatedly turns off reconnection 2. 3. **Describe the results you received:** Sometimes there are agent idle no connections still online **Describe the results you expected:** Make sure to close the channel offline every time the agent is idle and no connection **Additional information you deem important (e.g. issue happens only occasionally):** Occasional occurrence **Can you point out what caused this issue (optional)** Client sands off reconnected agent