[GH-ISSUE #3212] feautre not working

gitea-mirror commented

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

Owner

Copy link

Originally created by @7054company on GitHub (Dec 15, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3212

Bug Description

A i use
dashboard feauture by setup in frps.ini
It work well over port
But when i try to use admin ui feature it not work
It does not assign the port
And does not work ..

Can you fix that

frpc Version

latest release

frps Version

latest release

System Architecture

linux

Configurations

Simple setup not complex

Logs

No response

Steps to reproduce

nano frps.ini
add admin docs setup
now run
frps -c frps.ini
It does not assign or activate admin feature
...

Affected area

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

Originally created by @7054company on GitHub (Dec 15, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3212 ### Bug Description A i use dashboard feauture by setup in frps.ini It work well over port But when i try to use admin ui feature it not work It does not assign the port And does not work .. Can you fix that ### frpc Version latest release ### frps Version latest release ### System Architecture linux ### Configurations Simple setup not complex ### Logs _No response_ ### Steps to reproduce 1. nano frps.ini 2. add admin docs setup 3. now run 4. frps -c frps.ini 5. It does not assign or activate admin feature ... ### Affected area - [ ] Docs - [X] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [X] Test and Release - [X] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

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

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@Becods commented on GitHub (Dec 18, 2022):

Post your configuration.

@Becods commented on GitHub (Dec 18, 2022): Post your configuration.

gitea-mirror commented

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

Author

Owner

Copy link

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

gitea-mirror commented

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

Author

Owner

Copy link

@7054company commented on GitHub (Jan 19, 2023):

Wait i will soon response

@7054company commented on GitHub (Jan 19, 2023): Wait i will soon response

gitea-mirror commented

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

Author

Owner

Copy link

@7054company commented on GitHub (Jan 19, 2023):

[common]
bind_addr = 0.0.0.0
bind_port = 7000
bind_udp_port = 7001
kcp_bind_port = 7000

dashboard_addr = 0.0.0.0
dashboard_port = 7005
dashboard_user= admin
dashboard_pwd = admin
enable_prometheus = true

allow_ports = 2000-9000,4000-50000

detailed_errors_to_client = true

@7054company commented on GitHub (Jan 19, 2023): [common] bind_addr = 0.0.0.0 bind_port = 7000 bind_udp_port = 7001 kcp_bind_port = 7000 dashboard_addr = 0.0.0.0 dashboard_port = 7005 dashboard_user= admin dashboard_pwd = admin enable_prometheus = true allow_ports = 2000-9000,4000-50000 detailed_errors_to_client = true

gitea-mirror commented

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

Author

Owner

Copy link

@7054company commented on GitHub (Jan 19, 2023):

Bro i resolve that isssu but i have to ask how i assign random port to client fprc in ssh

@7054company commented on GitHub (Jan 19, 2023): Bro i resolve that isssu but i have to ask how i assign random port to client fprc in ssh

gitea-mirror commented

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

Author

Owner

Copy link

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

No Branch/Tag specified