[GH-ISSUE #2371] Show client login IP and run ID on dashboard #1884

Closed
opened 2026-05-05 13:13:02 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @ghost on GitHub (Apr 29, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2371

The solution you want

Show client login IP and run ID on dashboard
Alternatives considered

Maybe this is the simplest solution
How to implement this function

Update dashboard
Application scenarios of this function

Easy to monitor client (public FRP service)

Originally created by @ghost on GitHub (Apr 29, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2371 <!-- From Chinese to English by machine translation, welcome to revise and polish. --> **The solution you want** <!--A clear and concise description of the solution you want. --> Show client login IP and run ID on dashboard **Alternatives considered** <!--A clear and concise description of any alternative solutions or features you have considered. --> Maybe this is the simplest solution **How to implement this function** <!--Implementation steps for the solution you want. --> Update dashboard **Application scenarios of this function** <!--Make a clear and concise description of the application scenario of the solution you want. --> Easy to monitor client (public FRP service)
gitea-mirror 2026-05-05 13:13:02 -06:00
Author
Owner

@fatedier commented on GitHub (May 14, 2021):

You can set user = xxx in each frpc's config file to distinguish them. Every proxy name has user name prefix.

<!-- gh-comment-id:840964859 --> @fatedier commented on GitHub (May 14, 2021): You can set `user = xxx` in each frpc's config file to distinguish them. Every proxy name has user name prefix.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 29, 2021):

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

<!-- gh-comment-id:870139221 --> @github-actions[bot] commented on GitHub (Jun 29, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#1884
No description provided.