[GH-ISSUE #4627] [Feature Request] 希望可以支持wss转发 #3654

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

Originally created by @gladtoeatu on GitHub (Jan 8, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4627

Describe the feature request

内网开启了一个带ssl证书(mkcert生成的自签名)的wss端口27000,我通过frp将这个端口映射到了远端的27000端口,远端的27000端口又是用域名a.b.com/wss反代的,最终结果希望是可以用wss:/a.b.com/wss访问本地的27000端口的服务。目前这样访问会报400错误,如果把本地的wss改为ws(不要证书),是可以正常访问的

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 @gladtoeatu on GitHub (Jan 8, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4627 ### Describe the feature request 内网开启了一个带ssl证书(mkcert生成的自签名)的wss端口27000,我通过frp将这个端口映射到了远端的27000端口,远端的27000端口又是用域名a.b.com/wss反代的,最终结果希望是可以用wss:/a.b.com/wss访问本地的27000端口的服务。目前这样访问会报400错误,如果把本地的wss改为ws(不要证书),是可以正常访问的 ### Describe alternatives you've considered _No response_ ### Affected area - [X] 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:20:42 -06:00
Author
Owner

@filwu8 commented on GitHub (Jan 15, 2025):

你可以换一种思路,frp要结合 apache来用,内网机器27000端口用frp的 stcp 映射给 公网服务器,公网服务器用apche 升为wss
你内网的机器不用ssl'证书了。通过frp的stcp来确保 内网 和公网机器之间的链路安全。
image

<!-- gh-comment-id:2591465898 --> @filwu8 commented on GitHub (Jan 15, 2025): 你可以换一种思路,frp要结合 apache来用,内网机器27000端口用frp的 stcp 映射给 公网服务器,公网服务器用apche 升为wss 你内网的机器不用ssl'证书了。通过frp的stcp来确保 内网 和公网机器之间的链路安全。 <img width="637" alt="image" src="https://github.com/user-attachments/assets/841b4143-23a5-4516-9034-0dd9a4c51dcd" />
Author
Owner

@github-actions[bot] commented on GitHub (Jan 30, 2025):

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

<!-- gh-comment-id:2623259579 --> @github-actions[bot] commented on GitHub (Jan 30, 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#3654
No description provided.