[GH-ISSUE #2492] Configurable websocket PATH #1978

New issue

Closed

opened 2026-05-05 13:16:33 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 13:16:33 -06:00

Owner

Originally created by @osnosn on GitHub (Jul 22, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2492

Create a new config record for websocket PATH when working in WS mode.

New config record for server (frps),

websocket_path = /myfrp
or
websocket_path = /myfrp/aa23
( require start with '/', no space, up to 16 characters )

New config record for client (frpc), when protocol = websocket

websocket_path = /myfrp
( require start with '/', no space, up to 16 characters )

If this empty or not config, then use default path "/~!frp".

Originally created by @osnosn on GitHub (Jul 22, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2492 Create a new config record for websocket PATH when working in WS mode. New config record for server (frps), > websocket_path = /myfrp or websocket_path = /myfrp/aa23 ( require start with '/', no space, up to 16 characters ) New config record for client (frpc), when protocol = websocket > websocket_path = /myfrp ( require start with '/', no space, up to 16 characters ) If this empty or not config, then use default path "/~!frp".

gitea-mirror

2026-05-05 13:16:33 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:16:36 -06:00

Author

Owner

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