[GH-ISSUE #3530] The record of Network Traffic was lost after restarting the main program

gitea-mirror commented

2026-05-05 13:49:27 -06:00

Owner

Originally created by @ForestRealms on GitHub (Jul 16, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3530

Bug Description

After I have restart the frps program, the record of Network Traffic was lost.

The suggestion is save the record in a specific file and remain until the next day, instead of removing the recording immediately as I stopped the software.
Thank you

frpc Version

0.51.0

frps Version

0.51.0

System Architecture

linux/amd64

Configurations

# frps.ini
[common]
bind_port = 7000

[common]
dashboard_port = 7500
# dashboard's username and password are both optional
dashboard_user = root
dashboard_pwd = ************
dashboard_tls_mode = true
dashboard_tls_cert_file = server.crt
dashboard_tls_key_file = server.key
max_pool_count = 500
allow_ports = 3456,10000-64000
authentication_method = token
token = ************
enable_prometheus = true

# frpc.ini
[common]
server_addr = ***.***.***.***
server_port = 7000
authentication_method = token
admin_addr = 127.0.0.1
admin_port = 7400
admin_user = admin
admin_pwd = admin

[local-admin-ui]
type = tcp
local_ip = 127.0.0.1
local_port = 7400
remote_port = 3456
health_check_type = tcp
health_check_interval_s = 5
use_encryption = true
use_compression = true

[local-ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 10000
health_check_type = tcp
health_check_interval_s = 5
use_encryption = true
use_compression = true

[ESXi-1]
type = tcp
local_ip = 172.25.3.11
local_port = 443
remote_port = 11000
health_check_type = tcp
health_check_interval_s = 5
use_encryption = true
use_compression = true

[ESXi-2]
type = tcp
local_ip = 172.25.3.12
local_port = 443
remote_port = 12000
health_check_type = tcp
health_check_interval_s = 5
use_encryption = true
use_compression = true

[iDRAC-1]
type = tcp
local_ip = 172.25.3.1
local_port = 4430
remote_port = 11001
health_check_type = tcp
health_check_interval_s = 5
use_encryption = true
use_compression = true

[iDRAC-2]
type = tcp
local_ip = 172.25.3.2
local_port = 443
remote_port = 12001
health_check_type = tcp
health_check_interval_s = 5
use_encryption = true
use_compression = true

Logs

No response

Steps to reproduce

Stop the program by pressing "Ctrl+C", and re-start manually, and then visit the web dashboard.

Affected area

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

Originally created by @ForestRealms on GitHub (Jul 16, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3530 ### Bug Description After I have restart the `frps` program, the record of Network Traffic was lost. ![image](https://github.com/fatedier/frp/assets/97569905/5a0a7449-5792-44c1-abfc-8551222f17a0) The suggestion is save the record in a specific file and remain until the next day, instead of removing the recording immediately as I stopped the software. Thank you ### frpc Version 0.51.0 ### frps Version 0.51.0 ### System Architecture linux/amd64 ### Configurations ```ini # frps.ini [common] bind_port = 7000 [common] dashboard_port = 7500 # dashboard's username and password are both optional dashboard_user = root dashboard_pwd = ************ dashboard_tls_mode = true dashboard_tls_cert_file = server.crt dashboard_tls_key_file = server.key max_pool_count = 500 allow_ports = 3456,10000-64000 authentication_method = token token = ************ enable_prometheus = true ``` ```ini # frpc.ini [common] server_addr = ***.***.***.*** server_port = 7000 authentication_method = token admin_addr = 127.0.0.1 admin_port = 7400 admin_user = admin admin_pwd = admin [local-admin-ui] type = tcp local_ip = 127.0.0.1 local_port = 7400 remote_port = 3456 health_check_type = tcp health_check_interval_s = 5 use_encryption = true use_compression = true [local-ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 10000 health_check_type = tcp health_check_interval_s = 5 use_encryption = true use_compression = true [ESXi-1] type = tcp local_ip = 172.25.3.11 local_port = 443 remote_port = 11000 health_check_type = tcp health_check_interval_s = 5 use_encryption = true use_compression = true [ESXi-2] type = tcp local_ip = 172.25.3.12 local_port = 443 remote_port = 12000 health_check_type = tcp health_check_interval_s = 5 use_encryption = true use_compression = true [iDRAC-1] type = tcp local_ip = 172.25.3.1 local_port = 4430 remote_port = 11001 health_check_type = tcp health_check_interval_s = 5 use_encryption = true use_compression = true [iDRAC-2] type = tcp local_ip = 172.25.3.2 local_port = 443 remote_port = 12001 health_check_type = tcp health_check_interval_s = 5 use_encryption = true use_compression = true ``` ### Logs _No response_ ### Steps to reproduce Stop the program by pressing "Ctrl+C", and re-start manually, and then visit the web dashboard. ### Affected area - [ ] 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:49:27 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:49:30 -06:00

Author

Owner

@fatedier commented on GitHub (Jul 17, 2023):

This is not a core feature, and we don't have the resources to spend too much time on it.

@fatedier commented on GitHub (Jul 17, 2023): This is not a core feature, and we don't have the resources to spend too much time on it.

gitea-mirror commented

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

Author

Owner

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