[GH-ISSUE #4813] [Feature Request] 如何将grpc服务穿透到公网呢

gitea-mirror commented

2026-05-05 14:25:56 -06:00

Owner

Copy link

Originally created by @yibitnet on GitHub (May 26, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4813

Describe the feature request

如何将grpc服务穿透到公网呢
我本地部署了一个grpc服务，但是不知道如何配置，请教一下如何配置才行呢。
服务端frp已经安装好。起初我是使用type=tcp但是发现转发过来的流量无法获取到客户端的IP。导致无法双向请求grpc的客户端

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 @yibitnet on GitHub (May 26, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4813 ### Describe the feature request 如何将grpc服务穿透到公网呢我本地部署了一个grpc服务，但是不知道如何配置，请教一下如何配置才行呢。服务端frp已经安装好。起初我是使用type=tcp但是发现转发过来的流量无法获取到客户端的IP。导致无法双向请求grpc的客户端 ### 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 14:25:56 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:26:00 -06:00

Author

Owner

Copy link

@xqzr commented on GitHub (May 27, 2025):

gRPC 基于 HTTP/2

@xqzr commented on GitHub (May 27, 2025): gRPC 基于 HTTP/2

gitea-mirror commented

2026-05-05 14:26:00 -06:00

Author

Owner

Copy link

@yibitnet commented on GitHub (May 27, 2025):

gRPC 基于 HTTP/2
那是不是无法使用frp穿透到公网IP上了是吗

@yibitnet commented on GitHub (May 27, 2025): > gRPC 基于 HTTP/2 那是不是无法使用frp穿透到公网IP上了是吗

gitea-mirror commented

2026-05-05 14:26:01 -06:00

Author

Owner

Copy link

@xqzr commented on GitHub (May 27, 2025):

那是不是无法使用frp穿透到公网IP上了是吗

不是。意味着可以尝试 type: https

@xqzr commented on GitHub (May 27, 2025): > 那是不是无法使用frp穿透到公网IP上了是吗不是。意味着可以尝试 `type: https`

gitea-mirror commented

2026-05-05 14:26:02 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 11, 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 (Jun 11, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified