[GH-ISSUE #3407] [Feature Request] 改善 router config conflict 报错

gitea-mirror commented

2026-05-05 13:45:25 -06:00

Owner

Copy link

Originally created by @Daiyangcheng on GitHub (Apr 13, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3407

Describe the feature request

不知道有没有人遇到这个情况
客户端断网以后，服务端并没有及时释放连接，导致下一次链接的时候就会提示 router config conflict

很明显，我们希望能够在服务端中添加一个功能
就是通过检测心跳包的持续状态判断该客户端是否在线，若异常掉线就释放链接，以避免这个问题的出现
我发现之前有人提过这个问题，但是您并没有回复那个issue

同时也在这里提个建议，就是希望能够给心跳包一个容错的限度，服务器节点难免会有网络波动，如果一个心跳包没有成功接收就释放链接的话也会影响体验

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 @Daiyangcheng on GitHub (Apr 13, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3407 ### Describe the feature request 不知道有没有人遇到这个情况客户端断网以后，服务端并没有及时释放连接，导致下一次链接的时候就会提示 `router config conflict` 很明显，我们希望能够在服务端中添加一个功能就是通过检测心跳包的持续状态判断该客户端是否在线，若异常掉线就释放链接，以避免这个问题的出现我发现之前有人提过这个问题，但是您并没有回复那个issue 同时也在这里提个建议，就是希望能够给心跳包一个容错的限度，服务器节点难免会有网络波动，如果一个心跳包没有成功接收就释放链接的话也会影响体验 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:45:25 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:45:29 -06:00

Author

Owner

Copy link

@Daiyangcheng commented on GitHub (May 3, 2023):

@Daiyangcheng commented on GitHub (May 3, 2023): 1

gitea-mirror commented

2026-05-05 13:45:29 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 3, 2023):

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

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

No Branch/Tag specified