[GH-ISSUE #4874] [Feature Request] 可以允许通过frpc修改穿透到frps目标监听的地址吗? Is it possible to allow modifying the target listening address on frps via frpc? #3844

Closed
opened 2026-05-05 14:27:31 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @Moyuyanli on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4874

Describe the feature request

My question is, can we allow the ability to change the listening address of the tunnel on frps through frpc?

What I mean is, when setting up a tunnel from frpc to frps, could we have control over the listening address on the frps side? For example, changing it from 0.0.0.0 to 127.0.0.1.

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 @Moyuyanli on GitHub (Jul 9, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4874 ### Describe the feature request My question is, can we allow the ability to change the listening address of the tunnel on frps through frpc? What I mean is, when setting up a tunnel from frpc to frps, could we have control over the listening address on the frps side? For example, changing it from 0.0.0.0 to 127.0.0.1. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [x] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:27:31 -06:00
Author
Owner

@loveyacper commented on GitHub (Jul 11, 2025):

It's the issue I also concerned. You can set proxyBindAddr in frps config.

<!-- gh-comment-id:3060009678 --> @loveyacper commented on GitHub (Jul 11, 2025): It's the issue I also concerned. You can set `proxyBindAddr` in frps config.
Author
Owner

@github-actions[bot] commented on GitHub (Jul 26, 2025):

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

<!-- gh-comment-id:3120832045 --> @github-actions[bot] commented on GitHub (Jul 26, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3844
No description provided.