[GH-ISSUE #4117] http communication from frpc client to frps server

gitea-mirror commented

2026-05-05 14:05:47 -06:00

Owner

Copy link

Originally created by @testarchitecture39 on GitHub (Mar 31, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4117

Bug Description

is it possible to have http communication initiated from frpc endpoint and it goes to the frps server ?
i.e. the reverse communication from frpc to frps.
I have a use case where we want to call the frpc service which is in local network and the request should go to frps which is in public . Please suggest.

frpc Version

0.54.0

frps Version

0.54.0

System Architecture

Configurations

Logs

No response

Steps to reproduce

...

Affected area

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

Originally created by @testarchitecture39 on GitHub (Mar 31, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4117 ### Bug Description is it possible to have http communication initiated from frpc endpoint and it goes to the frps server ? i.e. the reverse communication from frpc to frps. I have a use case where we want to call the frpc service which is in local network and the request should go to frps which is in public . Please suggest. ### frpc Version 0.54.0 ### frps Version 0.54.0 ### System Architecture NA ### Configurations NA ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror

2026-05-05 14:05:47 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 22, 2024):

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

@github-actions[bot] commented on GitHub (Apr 22, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror commented

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

Author

Owner

Copy link

@remram44 commented on GitHub (Apr 22, 2024):

I am interested in this feature. chisel can do connections both ways, so can SSH and a few other tunneling options.

I would understand if this is out of scope but an answer would be appreciated.

@remram44 commented on GitHub (Apr 22, 2024): I am interested in this feature. [chisel](https://github.com/jpillora/chisel) can do connections both ways, so can SSH and a few other tunneling options. I would understand if this is out of scope but an answer would be appreciated.

gitea-mirror commented

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

Author

Owner

Copy link

@fatedier commented on GitHub (Apr 22, 2024):

@remram44 There are no plans for this in the short term. Currently, we are focusing on some major refactoring. Perhaps future versions will be able to support it based on the refactoring.

@fatedier commented on GitHub (Apr 22, 2024): @remram44 There are no plans for this in the short term. Currently, we are focusing on some major refactoring. Perhaps future versions will be able to support it based on the refactoring.

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (May 14, 2024):

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

@github-actions[bot] commented on GitHub (May 14, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:47:09 -06:00

[PR #3248] [MERGED] bump version #4705

No Branch/Tag specified