mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #2345] Websocket #1861
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#1861
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 @steom on GitHub (Apr 8, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2345
Connecting to frps via HTTP PROXY with frpc v0.36.2 websocket protocol does not work.
Not connect.
Successfull, all ok with frpc protocol set to tcp.
Set to websocket does not work.
I thought it was fixed in v0.35.0 (HTTP type proxy can't handle websocket protocol due to error Connection header value) but not, i think the Connection header still needs some fix.
@blizard863 commented on GitHub (Apr 9, 2021):
Please support error log.
@steom commented on GitHub (Apr 9, 2021):
[W] [service.go:104] login to server failed: websocket.Dial
ws://site.example.com:80/!frp: dial tcp 34.243.25.55:80: i/o timeout
websocket.Dial ws://site.example.com:80/~!frp: dial tcp 34.243.25.55:80: i/o timeout
@blizard863 commented on GitHub (Apr 9, 2021):
you can try nc -zv 11.22.33.44 80
@steom commented on GitHub (Apr 9, 2021):
Ncat: Version 7.80 ( https://nmap.org/ncat )
Ncat: Connected to 34.243.25.55:80.
Ncat: 0 bytes sent, 0 bytes received in 0.23 seconds.
@blizard863 commented on GitHub (Apr 11, 2021):
Maybe your http proxy cannot work.
@steom commented on GitHub (Apr 11, 2021):
Http proxy with frpc protocol = tcp works fine
Http proxy with frpc protocol = websocket no connection
@blizard863 commented on GitHub (Apr 11, 2021):
OK,I will try to test it locally.
@github-actions[bot] commented on GitHub (May 27, 2021):
Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.