[GH-ISSUE #5171] [Feature Request] Show client version in dashboard (0.67+)

gitea-mirror commented

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

Owner

Copy link

Originally created by @jay875037671 on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5171

Describe the feature request

Client version was displayed in the old dashboard.

Since v0.67, we have clientID, which is great, but the client version information is no longer shown.

Would it be possible to add the client version back to the new dashboard?
It is very useful for managing multiple clients and troubleshooting compatibility issues.

Thanks!

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 @jay875037671 on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5171 ### Describe the feature request Client version was displayed in the old dashboard. Since v0.67, we have clientID, which is great, but the client version information is no longer shown. Would it be possible to add the client version back to the new dashboard? It is very useful for managing multiple clients and troubleshooting compatibility issues. Thanks! ### 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:33:45 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 25, 2026):

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 (Feb 25, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified