mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #4947] heartbeatTimeout 设置后导致 0.58 之后 的版本不触发 ping 操作 #3899
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#3899
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @change41 on GitHub (Aug 20, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4947
Bug Description
当 frpc 配置 transport.heartbeatTimeout = 90 , 0.58.0 之后的版本不会向服务端发送 ping 健康检查
当换成 0.57 后
看了一下版本更新日志，应该是和这个优化有关系
frpc Version
frps Version
0.63.0
System Architecture
linux/amd64
Configurations
【frps】version: 0.63.0
#基础服务配置
bindAddr = "0.0.0.0"
bindPort = 7000
kcpBindPort = 7002
quicBindPort = 7000
transport.quic.keepalivePeriod = 10
transport.quic.maxIdleTimeout = 30
transport.quic.maxIncomingStreams = 100000
transport.maxPoolCount = 50
maxPortsPerClient = 0
subDomainHost = "frps.com"
udpPacketSize = 1500
transport.tcpMux = true
transport.tcpMuxKeepaliveInterval = 60
tcpmuxHTTPConnectPort = 7004
tcpmuxPassthrough = true
心跳设置
transport.heartbeatTimeout = 90
transport.tcpKeepalive = 180
虚拟主机相关配置，一般用于http/https 默认端口
vhostHTTPPort = 80
vhostHTTPSPort = 443
webServer.addr = "0.0.0.0"
webServer.port = 7002
webServer.user = "admin"
webServer.password = "password"
认证相关配置
auth.method = "token"
auth.additionalScopes = ["HeartBeats", "NewWorkConns"]
auth.token = "token123456"
Logs
【0.58.0】
root@zhiqingde:/etc/frp# ./frpc -v
0.58.0
root@zhiqingde:/etc/frp# systemctl restart frpc;tail -f /tmp/frpc.log
2025-08-20 21:24:22.380 [I] [sub/root.go:142] start frpc service for config file [/etc/frp/frpc.toml]
2025-08-20 21:24:22.380 [I] [client/service.go:295] try to connect to server...
2025-08-20 21:24:22.380 [I] [client/service.go:174] admin server listen on 0.0.0.0:7400
2025-08-20 21:24:22.485 [I] [client/service.go:287] [353d16b9426c2817] login to server success, get run id [353d16b9426c2817]
2025-08-20 21:24:22.485 [I] [proxy/proxy_manager.go:173] [353d16b9426c2817] proxy added: [zhy.ssh2]
2025-08-20 21:24:22.485 [I] [health/health.go:123] [353d16b9426c2817] [zhy.ssh2] health check status change to success
2025-08-20 21:24:22.486 [I] [proxy/proxy_wrapper.go:239] [353d16b9426c2817] [zhy.ssh2] health check success
2025-08-20 21:24:23.022 [I] [client/control.go:168] [353d16b9426c2817] [zhy.ssh2] start proxy success
2025-08-20 21:25:52.525 [I] [client/service.go:295] [353d16b9426c2817] try to connect to server...
2025-08-20 21:25:52.637 [I] [client/service.go:287] [353d16b9426c2817] login to server success, get run id [353d16b9426c2817]
2025-08-20 21:25:52.637 [I] [proxy/proxy_manager.go:173] [353d16b9426c2817] proxy added: [zhy.ssh2]
2025-08-20 21:25:52.637 [I] [health/health.go:123] [353d16b9426c2817] [zhy.ssh2] health check status change to success
2025-08-20 21:25:52.637 [I] [proxy/proxy_wrapper.go:239] [353d16b9426c2817] [zhy.ssh2] health check success
2025-08-20 21:25:53.171 [I] [client/control.go:168] [353d16b9426c2817] [zhy.ssh2] start proxy success
^C
root@zhiqingde:/etc/frp#
【frps】
2025-08-20 21:22:56,494 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '71d68ded403bcf7b'}, 'run_id': '71d68ded403bcf7b'}}
2025-08-20 21:24:22,472 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '353d16b9426c2817'}, 'run_id': '353d16b9426c2817'}}
2025-08-20 21:24:22,472 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '353d16b9426c2817'}, 'run_id': '353d16b9426c2817'}}
2025-08-20 21:25:52,626 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '353d16b9426c2817'}, 'run_id': '353d16b9426c2817'}}
2025-08-20 21:25:52,626 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '353d16b9426c2817'}, 'run_id': '353d16b9426c2817'}}
2025-08-20 21:27:22,821 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '353d16b9426c2817'}, 'run_id': '353d16b9426c2817'}}
===========================================================
【0.57.0】
root@zhiqingde:/etc/frp# ./frpc -v
0.57.0
root@zhiqingde:/etc/frp# systemctl restart frpc;tail -f /tmp/frpc.log
2025-08-20 21:27:42.275 [I] [sub/root.go:142] start frpc service for config file [/etc/frp/frpc.toml]
2025-08-20 21:27:42.275 [I] [client/service.go:294] try to connect to server...
2025-08-20 21:27:42.393 [I] [client/service.go:286] [9652c9453297ca7b] login to server success, get run id [9652c9453297ca7b]
2025-08-20 21:27:42.393 [I] [proxy/proxy_manager.go:173] [9652c9453297ca7b] proxy added: [zhy.ssh2]
2025-08-20 21:27:42.393 [I] [client/service.go:184] admin server listen on 0.0.0.0:7400
2025-08-20 21:27:42.396 [I] [health/health.go:123] [9652c9453297ca7b] [zhy.ssh2] health check status change to success
2025-08-20 21:27:42.396 [I] [proxy/proxy_wrapper.go:239] [9652c9453297ca7b] [zhy.ssh2] health check success
2025-08-20 21:27:42.928 [I] [client/control.go:170] [9652c9453297ca7b] [zhy.ssh2] start proxy success
【frps】
2025-08-20 21:27:22,821 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '353d16b9426c2817'}, 'run_id': '353d16b9426c2817'}}
2025-08-20 21:27:22,821 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '353d16b9426c2817'}, 'run_id': '353d16b9426c2817'}}
2025-08-20 21:27:42,380 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '9652c9453297ca7b'}, 'run_id': '9652c9453297ca7b'}}
2025-08-20 21:27:42,380 - INFO - {'version': '0.1.0', 'op': 'NewWorkConn', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '9652c9453297ca7b'}, 'run_id': '9652c9453297ca7b'}}
2025-08-20 21:27:42,383 - INFO - {'version': '0.1.0', 'op': 'Ping', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '9652c9453297ca7b'}}}
2025-08-20 21:27:42,383 - INFO - {'version': '0.1.0', 'op': 'Ping', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '9652c9453297ca7b'}}}
2025-08-20 21:28:12,382 - INFO - {'version': '0.1.0', 'op': 'Ping', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '9652c9453297ca7b'}}}
2025-08-20 21:28:12,382 - INFO - {'version': '0.1.0', 'op': 'Ping', 'content': {'user': {'user': 'zhy', 'metas': None, 'run_id': '9652c9453297ca7b'}}}
Steps to reproduce
...
Affected area
@github-actions[bot] commented on GitHub (Sep 4, 2025):
Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.