[GH-ISSUE #3426] How to remove offline client proxies from FRP dashboard

gitea-mirror commented

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

Owner

Originally created by @ksingh7 on GitHub (Apr 26, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3426

Bug Description

Every time when a FRP client connects and disconnects , it leaves an entry in FRP > Proxies list (API as well as dashboard). This entry stays forever , unless FRP server is restarted.

I am looking for a way to clear FRP client list that are offline , either by API call or a ini file parameter (that i am missing)

frpc Version

0.48

frps Version

0.48

System Architecture

linux/amd64

Configurations

frpc.ini

[common]
bind_port = 7000
#vhost_http_port = 8000
subdomain_host = xxxx.cn
tls_enable = true
token = xxxx
# Frps Dashboard
dashboard_addr = 0.0.0.0
dashboard_port = 7500
# dashboard user and passwd for basic auth protect
dashboard_user = admin
dashboard_pwd = xxxx

# Frps Logs
#log_file = /var/log/frps.log
# trace, debug, info, warn, error
log_level = debug
log_max_days = 3

allow_ports = 30001-30025
#max_ports_per_client = 2
max_pool_count = 10

frpc.ini

[common]
server_addr = xxxx
server_port = 7000
tls_enable = true
token = xxxx

[client-30001]
type = tcp
local_ip = 127.0.0.1
local_port = 8888
remote_port = 30001
use_encryption = true
use_compression = true

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @ksingh7 on GitHub (Apr 26, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3426 ### Bug Description Every time when a FRP client connects and disconnects , it leaves an entry in FRP > Proxies list (API as well as dashboard). This entry stays forever , unless FRP server is restarted. I am looking for a way to clear FRP client list that are offline , either by API call or a ini file parameter (that i am missing) <img width="1728" alt="image" src="https://user-images.githubusercontent.com/9701902/234446819-2ec2c935-8494-4e6b-8094-70c17106e27d.png"> ### frpc Version 0.48 ### frps Version 0.48 ### System Architecture linux/amd64 ### Configurations - frpc.ini ``` [common] bind_port = 7000 #vhost_http_port = 8000 subdomain_host = xxxx.cn tls_enable = true token = xxxx # Frps Dashboard dashboard_addr = 0.0.0.0 dashboard_port = 7500 # dashboard user and passwd for basic auth protect dashboard_user = admin dashboard_pwd = xxxx # Frps Logs #log_file = /var/log/frps.log # trace, debug, info, warn, error log_level = debug log_max_days = 3 allow_ports = 30001-30025 #max_ports_per_client = 2 max_pool_count = 10 ``` - frpc.ini ``` [common] server_addr = xxxx server_port = 7000 tls_enable = true token = xxxx [client-30001] type = tcp local_ip = 127.0.0.1 local_port = 8888 remote_port = 30001 use_encryption = true use_compression = true ``` ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [X] 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 13:45:57 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:46:00 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 26, 2023):

0214b974dd/pkg/metrics/mem/server.go (L77)

It will be cleaned periodically, with a reserved time hard-coded for 7 days.

@fatedier commented on GitHub (Apr 26, 2023): https://github.com/fatedier/frp/blob/0214b974ddd928f74f0922dd28ee8aa9e5b0743f/pkg/metrics/mem/server.go#L77 It will be cleaned periodically, with a reserved time hard-coded for 7 days.

gitea-mirror commented

2026-05-05 13:46:02 -06:00

Author

Owner

@ksingh7 commented on GitHub (Apr 26, 2023):

Thanks @fatedier for response.

@ksingh7 commented on GitHub (Apr 26, 2023): Thanks @fatedier for response.

gitea-mirror commented

2026-05-05 13:46:03 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (May 27, 2023):

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