[GH-ISSUE #4713] 请教一个问题：如何监听客户端frpc和frps的通信状态

gitea-mirror commented

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

Owner

Copy link

Originally created by @ebfming on GitHub (Mar 15, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4713

Describe the feature request

使用场景：我通过远程修改frpc.ini配置文件，结果不小心改错了，也没测试直接更新了服务
结果导致客户端和服务端无法握手...

为避免这种情况，我想要写一个sh脚本，用来监听frpc和frps的通信状态，如果发现frpc和frps无法通信，那么
1、通过原来的frpc.ini.bak恢复现在用的frpc.ini
2、通过 systemctl restart frpc 重启程序

我想知道frp有提供类似的接口来监听状态吗？

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @ebfming on GitHub (Mar 15, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4713 ### Describe the feature request 使用场景：我通过远程修改frpc.ini配置文件，结果不小心改错了，也没测试直接更新了服务结果导致客户端和服务端无法握手... --- 为避免这种情况，我想要写一个sh脚本，用来监听frpc和frps的通信状态，如果发现frpc和frps无法通信，那么 1、通过原来的frpc.ini.bak恢复现在用的frpc.ini 2、通过 systemctl restart frpc 重启程序 --- 我想知道frp有提供类似的接口来监听状态吗？ ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

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

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@aila00814 commented on GitHub (Mar 16, 2025):

可以使用客户端管理界面查看客户端的proxy状态根据状态判断frpc和frps的通信状态

@aila00814 commented on GitHub (Mar 16, 2025): 可以使用[客户端管理界面](https://gofrp.org/zh-cn/docs/features/common/ui/)查看客户端的proxy状态根据状态判断frpc和frps的通信状态

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Mar 30, 2025):

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

@github-actions[bot] commented on GitHub (Mar 30, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:49:16 -06:00

[PR #3722] [MERGED] bump version #4815

gitea-mirror referenced this issue

2026-05-05 14:49:16 -06:00

[PR #3721] [MERGED] rename example configuration file name #4816

No Branch/Tag specified