[GH-ISSUE #2984] [Feature Request] 希望在frpc内加入备用server-addr支持

gitea-mirror commented

2026-05-05 13:31:53 -06:00

Owner

Copy link

Originally created by @coolxy on GitHub (Jun 16, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2984

Describe the feature request

设置了frps服务器的重启，指向服务器的域名有多个，服务器重启后个别域名解析慢了点，能不能加入备用域名支持，当联不上一个时去连接另一个。

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 @coolxy on GitHub (Jun 16, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2984 ### Describe the feature request 设置了frps服务器的重启，指向服务器的域名有多个，服务器重启后个别域名解析慢了点，能不能加入备用域名支持，当联不上一个时去连接另一个。 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:31:53 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:31:56 -06:00

Author

Owner

Copy link

@aa51513 commented on GitHub (Jun 28, 2022):

If possible, I also very much expect developers to support this feature

@aa51513 commented on GitHub (Jun 28, 2022): If possible, I also very much expect developers to support this feature

gitea-mirror commented

2026-05-05 13:31:57 -06:00

Author

Owner

Copy link

@supply9243 commented on GitHub (Jul 7, 2022):

既然是多个域名指向同一个服务器/IP，为何不直接多域名CNAME一个呢？
如果是多个服务器使用备用连接还稍微有点意义，但好像不能确定FRPC连接了哪台。
担心服务器出问题不知道建议用 uptime。

@supply9243 commented on GitHub (Jul 7, 2022): 既然是多个域名指向同一个服务器/IP，为何不直接多域名CNAME一个呢？如果是多个服务器使用备用连接还稍微有点意义，但好像不能确定FRPC连接了哪台。担心服务器出问题不知道建议用 uptime。

gitea-mirror commented

2026-05-05 13:31:58 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 7, 2022):

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 (Aug 7, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:44:59 -06:00

[PR #2520] [MERGED] frpc: add disable_custom_tls_first_byte to not send first custom tls byte to frps #4592

No Branch/Tag specified