[GH-ISSUE #3939] [Feature Request] 服务器网络异常时，重试时间是如何确定的？

gitea-mirror commented

2026-05-05 14:01:28 -06:00

Owner

Copy link

Originally created by @liqilong2017 on GitHub (Jan 17, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3939

Describe the feature request

请问，客户端的服务器网络异常时，多长时间会重试去连服务器端，重试时间是如何确定的？
文档里没有找到相关的配置

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 @liqilong2017 on GitHub (Jan 17, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/3939 ### Describe the feature request 请问，客户端的服务器网络异常时，多长时间会重试去连服务器端，重试时间是如何确定的？文档里没有找到相关的配置 ### 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 14:01:28 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:01:31 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Jan 17, 2024):

f7efbfeec5/client/service.go (L188-L217)

@Becods commented on GitHub (Jan 17, 2024): https://github.com/fatedier/frp/blob/f7efbfeec53b64b85b256124b896430289933757/client/service.go#L188-L217

gitea-mirror commented

2026-05-05 14:01:32 -06:00

Author

Owner

Copy link

@superzjg commented on GitHub (Jan 17, 2024):

上面有列出代码。
其实你可以自己看log文件，先让frpc连上服务器，再把frps服务器关掉，（frpc配置 loginFailExit = false ，这个非必要）然后看frpc的log，会有具体“等待多少秒重试”之类的log。

@superzjg commented on GitHub (Jan 17, 2024): 上面有列出代码。其实你可以自己看log文件，先让frpc连上服务器，再把frps服务器关掉，（frpc配置 `loginFailExit = false` ，这个非必要）然后看frpc的log，会有具体“等待多少秒重试”之类的log。

gitea-mirror commented

2026-05-05 14:01:33 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 8, 2024):

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

@github-actions[bot] commented on GitHub (Feb 8, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified