[GH-ISSUE #5092] FRP Websocket issue

gitea-mirror commented

2026-05-05 14:32:32 -06:00

Owner

Copy link

Originally created by @neokd on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5092

Bug Description

I’m trying to expose a WebSocket service running on my home server to the internet using FRP. However, I’m running into issues with both ws and wss connections.

When connecting through FRP, the WebSocket request is rejected and closes with code 1006.

On the backend service, the WebSocket server logs show: “connection rejected (403 Forbidden)”.

Here’s the screenshot of the browser console/network tab showing the failed request:

frpc Version

0.61.1

frps Version

0.61.1

System Architecture

linux/amd64

Affected area

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

Originally created by @neokd on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5092 ### Bug Description I’m trying to expose a WebSocket service running on my home server to the internet using FRP. However, I’m running into issues with both ws and wss connections. When connecting through FRP, the WebSocket request is rejected and closes with code 1006. On the backend service, the WebSocket server logs show: “connection rejected (403 Forbidden)”. Here’s the screenshot of the browser console/network tab showing the failed request: <img width="1316" height="82" alt="Image" src="https://github.com/user-attachments/assets/128fc9f8-1d39-4478-b3a5-a7cd121b822e" /> ### frpc Version 0.61.1 ### frps Version 0.61.1 ### System Architecture linux/amd64 ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [x] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [x] Client Plugin - [x] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:32:32 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:32:35 -06:00

Author

Owner

Copy link

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

gitea-mirror referenced this issue

2026-05-05 14:50:31 -06:00

[PR #3999] [MERGED] Updated readme for the HTTP Proxy #4880

gitea-mirror referenced this issue

2026-05-05 14:50:54 -06:00

[PR #4056] [MERGED] bump version #4902

No Branch/Tag specified