[GH-ISSUE #4715] [Feature Request] 在 frpc 客户端日志上记录 userConn 信息（实际访问用户的真实地址）？

gitea-mirror commented

2026-05-05 14:23:17 -06:00

Owner

Copy link

Originally created by @shunf4 on GitHub (Mar 16, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4715

Describe the feature request

目前 frps 在（DEBUG）日志里记录了 userConn 信息（实际访问用户的真实 IP），但 frpc 的日志里并没有（只记录了 localConn 和 workConn，对识别实际访问者的实际意义较小），这导致使用 freefrp 等公用穿透服务时，服务暴露者没有 frps 的日志查看权，如果没需求使用 PROXY Protocol，似乎就没法知道访问者真实地址了。就算有 frps 的日志查看权，想追踪内网服务的访问源时常需要两台机器的日志对照着看，造成不便。

当前 frp 的架构设计，应该是已经将访问者的实际地址（IP+端口）传递到了客户端的，那 frpc 是否能在日志里打印这些信息？

Describe alternatives you've considered

有 frps 机器登录权限的话可以串流服务端日志到 frpc 机器。如果没有 frps 权限则没有替代方案。

Affected area

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

Originally created by @shunf4 on GitHub (Mar 16, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4715 ### Describe the feature request 目前 frps 在（DEBUG）日志里记录了 userConn 信息（实际访问用户的真实 IP），但 frpc 的日志里并没有（只记录了 localConn 和 workConn，对识别实际访问者的实际意义较小），这导致使用 freefrp 等公用穿透服务时，服务暴露者没有 frps 的日志查看权，如果没需求使用 PROXY Protocol，似乎就没法知道访问者真实地址了。就算有 frps 的日志查看权，想追踪内网服务的访问源时常需要两台机器的日志对照着看，造成不便。当前 frp 的架构设计，应该是已经将访问者的实际地址（IP+端口）传递到了客户端的，那 frpc 是否能在日志里打印这些信息？ ### Describe alternatives you've considered 有 frps 机器登录权限的话可以串流服务端日志到 frpc 机器。如果没有 frps 权限则没有替代方案。 ### 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 14:23:17 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Mar 31, 2025):

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

@github-actions[bot] commented on GitHub (Mar 31, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:23:22 -06:00

Author

Owner

Copy link

@shunf4 commented on GitHub (Mar 31, 2025):

bump

@shunf4 commented on GitHub (Mar 31, 2025): bump

gitea-mirror commented

2026-05-05 14:23:23 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 16, 2025):

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

@github-actions[bot] commented on GitHub (Apr 16, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified