mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #4501] Cannot handle Websocket traffic #3554
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#3554
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JobberRT on GitHub (Oct 18, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4501
Bug Description
frpccannot handle websocket traffic in bothtransport.protocol=tcpandtransport.protocol=websocket. Websocket server indicates thatWebsocket Handshake Not Finished.frpc Version
0.60.0
frps Version
0.60.0
System Architecture
linux/amd64
Configurations
frpc.ini
A frpc proxy config example(using rustdesk as example)
Logs
frpc log
rustdesk log
Steps to reproduce
No response
Affected area
@JobberRT commented on GitHub (Oct 18, 2024):
The same problem can also be found when using portainer's web terminal
@JobberRT commented on GitHub (Oct 19, 2024):
A further digging tells that If the
frpcand its service are on the same private network, websocket will success. For example,frpcandportainerandrustdeskare both in the same network:172.10.0.0/24. (Forrustdesk, thehbbr/hbbs/frpc/controlled clientmust be at the same network, thecontrolling clientmay not)I start to wonder if the problem is caused by my VPS provider, will check later
@JobberRT commented on GitHub (Oct 19, 2024):
Somehow after restarting the
portainerand thefrpc,portainer's websocket connection become availableI also tried to reinstall the docker, recreate a new
frpcandrustdeskcontainer, butrustdesk's webscoket cannot become available likeportainer.And for why
rustdeskwebsocket is available whenfrpcand the services are in the same network, I verified that its becauserustdeskuse direct-peering(p2p). After disable the direct-peering, rustdesk become compelete unusable. Besides that, the websocket-available-inside-same-network behavior changed, it requires the controlling client inside the same network as well.I guess this is not a VPS issue, but a
rustdeskissue, I will go to their repo and submit an issue to see if I can get the answer. Meanwhile, I will keep this issue open and close it after I get a positive answer(With the solution if I get one)@fatedier commented on GitHub (Oct 21, 2024):
For proxies of type
tcp, frp does not modify any transmitted content.Generally speaking, if issues arise, they are mostly related to application layer logic, such as restricting access by IP or relying on specific network links.
@JobberRT commented on GitHub (Oct 21, 2024):
@fatedier Thanks for the reply, I've read the code of frp and understand your point. And now I'm setting up some test env to dig further
@JobberRT commented on GitHub (Oct 31, 2024):
I will close this issue since I'm been super busy lately, and I will update the information if I have time and find something later
@k-nearest-neighbor commented on GitHub (Oct 30, 2025):
run.