#2342 - [GH-ISSUE #2936] client - server connection uses tcp even protocol = websocket applied in client configuration. - github-starred/frp

gitea-mirror commented

2026-05-05 13:30:39 -06:00

Owner

Copy link

Originally created by @anand-010 on GitHub (May 13, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2936

Bug Description

I am trying to connect frp client to server using WebSocket protocol because of some routing in server.
I've setted protocol = websocket in the client ini configuraion.
The connection was successfull but in the wireshark i've noted that there is no http or http upgradation requests send.
only tcp packts are visible.

frpc Version

0.38.0

frps Version

0.38.0

System Architecture

client windows/amd64 , server linux/amd64

Configurations

[common]
server_addr = xxxxxx
server_port = 7000
protocol = websocket
token = secrettoken
meta_token = 6204d237642c6d139c8b00bf
user = xxx
[web]
type = http
local_port = 8000
subdomain = xxx

Logs

2022/05/13 11:19:45 [I] [service.go:301] [72ba4091e96f96f8] login to server success, get run id [72ba4091e96f96f8], server udp port [0]
2022/05/13 11:19:45 [I] [proxy_manager.go:144] [72ba4091e96f96f8] proxy added: [xxxx]
2022/05/13 11:19:46 [I] [control.go:180] [72ba4091e96f96f8] [xxxx] start proxy success

Steps to reproduce

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 @anand-010 on GitHub (May 13, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2936 ### Bug Description I am trying to connect frp client to server using WebSocket protocol because of some routing in server. I've setted protocol = websocket in the client ini configuraion. The connection was successfull but in the wireshark i've noted that there is no http or http upgradation requests send. only tcp packts are visible. ![rrr](https://user-images.githubusercontent.com/32414977/168222110-5fc0472e-ad18-479d-aecc-83414e702fb6.PNG) ### frpc Version 0.38.0 ### frps Version 0.38.0 ### System Architecture client windows/amd64 , server linux/amd64 ### Configurations [common] server_addr = xxxxxx server_port = 7000 protocol = websocket token = secrettoken meta_token = 6204d237642c6d139c8b00bf user = xxx [web] type = http local_port = 8000 subdomain = xxx ### Logs 2022/05/13 11:19:45 [I] [service.go:301] [72ba4091e96f96f8] login to server success, get run id [72ba4091e96f96f8], server udp port [0] 2022/05/13 11:19:45 [I] [proxy_manager.go:144] [72ba4091e96f96f8] proxy added: [xxxx] 2022/05/13 11:19:46 [I] [control.go:180] [72ba4091e96f96f8] [xxxx] start proxy success ### Steps to reproduce _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 13:30:39 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:30:42 -06:00

Author

Owner

Copy link

@anand-010 commented on GitHub (May 13, 2022):

I've found that WebSocket is not being implemented it yet.
service.go line 259.

Please add this feature.

@anand-010 commented on GitHub (May 13, 2022): I've found that WebSocket is not being implemented it yet. service.go line 259. ![mmmm](https://user-images.githubusercontent.com/32414977/168246993-f0e46938-c2cb-4e2f-8be9-b067322dece5.PNG) Please add this feature.

gitea-mirror commented

2026-05-05 13:30:43 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 13, 2022):

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

No Branch/Tag specified