[GH-ISSUE #2660] [Feature Request] 直接转发本地端口

gitea-mirror commented

2026-05-05 13:21:45 -06:00

Owner

Copy link

Originally created by @jerry-wolf on GitHub (Nov 15, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2660

Describe the feature request

比如 a.example.com 在 frps 所在的服务器上，而 b.example.com 由通过 frpc 连接到 frps 然后在 frps 所在的服务器上提供服务，a.example.com 可以直接由 frps 转发。

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 @jerry-wolf on GitHub (Nov 15, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2660 ### Describe the feature request 比如 a.example.com 在 frps 所在的服务器上，而 b.example.com 由通过 frpc 连接到 frps 然后在 frps 所在的服务器上提供服务，a.example.com 可以直接由 frps 转发。 ### Describe alternatives you've considered 目前可以在 frps 所在的服务器上安装 frpc 并连接到当前服务器上的 frps 实现，只是它产生了额外的开销。 ### Affected area - [X] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:21:45 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

@blizard863 commented on GitHub (Nov 16, 2021):

听下来感觉你这个场景更适合用 NGINX ？

@blizard863 commented on GitHub (Nov 16, 2021): 听下来感觉你这个场景更适合用 NGINX ？

gitea-mirror commented

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

Author

Owner

Copy link

@jerry-wolf commented on GitHub (Nov 16, 2021):

如果仅仅是根据 Host 头或者 SNI 分流，那 Nginx 确实感觉更合适，但是还有部分名称还是需要转发到远程啊！

@jerry-wolf commented on GitHub (Nov 16, 2021): 如果仅仅是根据 Host 头或者 SNI 分流，那 Nginx 确实感觉更合适，但是还有部分名称还是需要转发到远程啊！

gitea-mirror commented

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

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Dec 17, 2021):

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 (Dec 17, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

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

[PR #3503] [MERGED] support wss between frpc and frps #4764

No Branch/Tag specified