[GH-ISSUE #2345] Websocket #1861

Closed
opened 2026-05-05 13:12:17 -06:00 by gitea-mirror · 8 comments
Owner

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.

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.
gitea-mirror 2026-05-05 13:12:17 -06:00
Author
Owner

@blizard863 commented on GitHub (Apr 9, 2021):

Please support error log.

<!-- gh-comment-id:816442192 --> @blizard863 commented on GitHub (Apr 9, 2021): Please support error log.
Author
Owner

@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

<!-- gh-comment-id:816448083 --> @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
Author
Owner

@blizard863 commented on GitHub (Apr 9, 2021):

you can try nc -zv 11.22.33.44 80

<!-- gh-comment-id:816623473 --> @blizard863 commented on GitHub (Apr 9, 2021): you can try nc -zv 11.22.33.44 80
Author
Owner

@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.

<!-- gh-comment-id:816627696 --> @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.
Author
Owner

@blizard863 commented on GitHub (Apr 11, 2021):

Maybe your http proxy cannot work.

<!-- gh-comment-id:817239861 --> @blizard863 commented on GitHub (Apr 11, 2021): Maybe your http proxy cannot work.
Author
Owner

@steom commented on GitHub (Apr 11, 2021):

Http proxy with frpc protocol = tcp works fine
Http proxy with frpc protocol = websocket no connection

<!-- gh-comment-id:817262803 --> @steom commented on GitHub (Apr 11, 2021): Http proxy with frpc protocol = tcp works fine Http proxy with frpc protocol = websocket no connection
Author
Owner

@blizard863 commented on GitHub (Apr 11, 2021):

OK,I will try to test it locally.

<!-- gh-comment-id:817268565 --> @blizard863 commented on GitHub (Apr 11, 2021): OK,I will try to test it locally.
Author
Owner

@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.

<!-- gh-comment-id:849212321 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#1861
No description provided.