[GH-ISSUE #4663] Why visitors are not displayed in the frpc admin ui?

gitea-mirror commented

2026-05-05 14:21:48 -06:00

Owner

Originally created by @fenghan0430 on GitHub (Feb 9, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4663

Describe the feature request

Why visitors are not displayed in the frpc admin ui?

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 @fenghan0430 on GitHub (Feb 9, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4663 ### Describe the feature request Why visitors are not displayed in the frpc admin ui? ### 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 - [x] Others

gitea-mirror closed this issue

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

gitea-mirror commented

2026-05-05 14:21:51 -06:00

Author

Owner

@starworld99 commented on GitHub (Feb 9, 2025):

please enable frpc log to get more info

@starworld99 commented on GitHub (Feb 9, 2025): please enable frpc log to get more info

gitea-mirror commented

2026-05-05 14:21:52 -06:00

Author

Owner

@fenghan0430 commented on GitHub (Feb 9, 2025):

Let me describe my question more fully.

To be clear, I have had no problems with frp. What I want to know is about the design of frp.

When I was using the frpc admin ui, I found visitors about stcp, xtcp (used on the receiving client). The configuration is usually as follows:

[[visitors]]
name = "secret_ssh_visitor"
type = "stcp"
serverName = "secret_ssh"
secretKey = "abcdefg"
bindAddr = "127.0.0.1"
bindPort = 6000

Such a configuration does not appear in the admin ui tunnel category, as shown in the figure below:

I don't know much about the design of frp and I wonder if there is any reason why this visitor doesn't show up in the tunnel list? Like it could cause a security breach or something.

I ask these questions because I am developing a tool to centrally manage multiple frpc client tunnels. I want to avoid safety hazards by design.

thank.

@fenghan0430 commented on GitHub (Feb 9, 2025): Let me describe my question more fully. To be clear, I have had no problems with frp. What I want to know is about the design of frp. When I was using the frpc admin ui, I found visitors about stcp, xtcp (used on the receiving client). The configuration is usually as follows: ```toml [[visitors]] name = "secret_ssh_visitor" type = "stcp" serverName = "secret_ssh" secretKey = "abcdefg" bindAddr = "127.0.0.1" bindPort = 6000 ``` Such a configuration does not appear in the admin ui tunnel category, as shown in the figure below: ![Image](https://github.com/user-attachments/assets/548c3efe-9ece-4752-a51a-fa58a35562e2) I don't know much about the design of frp and I wonder if there is any reason why this visitor doesn't show up in the tunnel list? Like it could cause a security breach or something. I ask these questions because I am developing a tool to centrally manage multiple frpc client tunnels. I want to avoid safety hazards by design. thank.

gitea-mirror commented

2026-05-05 14:21:53 -06:00

Author

Owner

@fatedier commented on GitHub (Feb 10, 2025):

Yes, it's not currently displayed. The web page is not the focus at the moment, and its functionality is incomplete.

@fatedier commented on GitHub (Feb 10, 2025): Yes, it's not currently displayed. The web page is not the focus at the moment, and its functionality is incomplete.

gitea-mirror commented

2026-05-05 14:21:54 -06:00

Author

Owner

@fenghan0430 commented on GitHub (Feb 10, 2025):

Thanks a lot

@fenghan0430 commented on GitHub (Feb 10, 2025): Thanks a lot

gitea-mirror referenced this issue

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

[PR #3682] [MERGED] fix encryption and compresion in dashboard #4808

gitea-mirror referenced this issue

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