mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #3957] Reverse proxy a VPN or Fiddler connection reset by peer #3140
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#3140
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 @crazy-dragon on GitHub (Jan 29, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3957
Bug Description
Bug Description
I want to use frp to share a vpn with others and first I run a VPN in my client(computer or my phone) and run frpc, then in my aliyun server I run the frps. And, I use a third device config a http proxy. It can work and I can use google, but some website cannot access (such as www.v2ex.com, youtube can't play video), and browser says ERR_CONNECTION_RESET. I try to use fiddler replace a VPN, but the result is same.
And I found websites that cannot be accessed or display abnormally using the HTTP2 protocol. Here is two screenshots of my visits v2ex and google. One fail and One success.
frpc Version
0.53.2
frps Version
0.53.2
System Architecture
server: linux/amd64 client:windows/amd64
Configurations
serverAddr = "my.server.ip"
serverPort = 10020
proxies
name = "test-tcp"
type = "tcp"
localIP = "127.0.0.1"
localPort = 10809
remotePort = 10021
Logs
No response
Steps to reproduce
Affected area
@fatedier commented on GitHub (Jan 30, 2024):
For TCP proxy, frp simply forwards traffic without recognizing specific protocols. Therefore, if there are any issues, it is likely to be a problem at the application layer.
@crazy-dragon commented on GitHub (Jan 30, 2024):
OK, I also think it's may a problem at the application layer. So, thanks you for you reply.