[GH-ISSUE #3849] [Feature Request] Hide FRPC Client Real IP Address because Rate Limit in DIP

gitea-mirror commented

2026-05-05 13:58:40 -06:00

Owner

Copy link

Originally created by @ashkan-moghadasi on GitHub (Dec 15, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3849

Describe the feature request

Because DIP has a rate limit on the ip address of some data centers. We need a feature to hide our external server IP address from DIP Perspective.

In reverse proxy mode when frpc client connects to frp server and its IP address belongs to hetzner or digital occasion. DIP will have a rate limit in this connection. Traffic between client and server transfer with a limited speed.

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 @ashkan-moghadasi on GitHub (Dec 15, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3849 ### Describe the feature request Because DIP has a rate limit on the ip address of some data centers. We need a feature to hide our external server IP address from DIP Perspective. In reverse proxy mode when frpc client connects to frp server and its IP address belongs to hetzner or digital occasion. DIP will have a rate limit in this connection. Traffic between client and server transfer with a limited speed. ### 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

gitea-mirror

2026-05-05 13:58:40 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:58:43 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Dec 18, 2023):

I don't think we can achieve this capability.

@fatedier commented on GitHub (Dec 18, 2023): I don't think we can achieve this capability.

gitea-mirror commented

2026-05-05 13:58:44 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 18, 2024):

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, 2024): 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:58:45 -06:00

Author

Owner

Copy link

@yuzhoua commented on GitHub (Nov 16, 2024):

Is there a solution to this problem now?

@yuzhoua commented on GitHub (Nov 16, 2024): Is there a solution to this problem now?

No Branch/Tag specified