[GH-ISSUE #3037] [Feature Request] 服务端frps的UI管理界面是否有考虑新增更多的管理和维护功能，而不必手工修改ini配置文件

gitea-mirror commented

2026-05-05 13:33:39 -06:00

Owner

Copy link

Originally created by @xzxiaoshan on GitHub (Jul 28, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3037

Describe the feature request

1、服务端frps的UI管理界面是否有考虑新增更多的管理和维护功能，而不必手工修改ini配置文件
2、是否有考虑将多用户插件集成到frps中，并增加对应的UI用户管理功能。

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 @xzxiaoshan on GitHub (Jul 28, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3037 ### Describe the feature request 1、服务端frps的UI管理界面是否有考虑新增更多的管理和维护功能，而不必手工修改ini配置文件 2、是否有考虑将多用户插件集成到frps中，并增加对应的UI用户管理功能。 ### 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 13:33:39 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:33:42 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Jul 28, 2022):

https://github.com/fatedier/frp/issues/1570

v0.31.0 已支持服务端插件，可以自行实现。

https://github.com/fatedier/frp/issues/3033

Planned in frp v2, we want to support multiple configure registry such as static file, remote url, etc.

@Becods commented on GitHub (Jul 28, 2022): https://github.com/fatedier/frp/issues/1570 > v0.31.0 已支持服务端插件，可以自行实现。 https://github.com/fatedier/frp/issues/3033 > Planned in frp v2, we want to support multiple configure registry such as static file, remote url, etc.

gitea-mirror commented

2026-05-05 13:33:43 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 28, 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 28, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified