github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #2007] FRPC_v0.34.0_反向代理发出故障 #1595

New issue

Closed

opened 2026-05-05 13:01:02 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 13:01:02 -06:00

Owner

Originally created by @gbh19930406 on GitHub (Sep 24, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2007

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?

0.34.0

What operating system and processor architecture are you using (go env)?

Linux arm64 & Windows amd64

Configures you used:

I used http and stcp to make the connect, it works perfect with FRPC 0.33.0

Steps to reproduce the issue:

Upgrade frps from 0.33.0 to 0.34.0
Upgrade frpc from 0.33.0 to 0.34.0
Failed to use rdp and http to make the connect
Downgrade frpc from 0.34.0 to 0.33.0
Succeed to use rdp and http to make the connect

Describe the results you received:

With FRPS 0.34.0 & FRPC 0.34.0

RDP with internal error
HTTP with error as well

With FRPS 0.34.0 & FRPC 0.33.0

Error Not found

Describe the results you expected:

Fix the issue of FRPC 0.34.0 cannot transfer the proxy data

Additional information you deem important (e.g. issue happens only occasionally):

FRPC file size about 0.34.0 is smaller than 0.33.0

Can you point out what caused this issue (optional)

Unknown root cause of this issue, may be changed or replaced or missed some core functions between these two versions.

Originally created by @gbh19930406 on GitHub (Sep 24, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2007 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** 0.34.0 **What operating system and processor architecture are you using (`go env`)?** Linux arm64 & Windows amd64 **Configures you used:** I used http and stcp to make the connect, it works perfect with FRPC 0.33.0 **Steps to reproduce the issue:** 1. Upgrade frps from 0.33.0 to 0.34.0 2. Upgrade frpc from 0.33.0 to 0.34.0 3. Failed to use rdp and http to make the connect 4. Downgrade frpc from 0.34.0 to 0.33.0 5. Succeed to use rdp and http to make the connect **Describe the results you received:** With FRPS 0.34.0 & FRPC 0.34.0 1. RDP with internal error 2. HTTP with error as well With FRPS 0.34.0 & FRPC 0.33.0 Error Not found **Describe the results you expected:** Fix the issue of FRPC 0.34.0 cannot transfer the proxy data **Additional information you deem important (e.g. issue happens only occasionally):** FRPC file size about 0.34.0 is smaller than 0.33.0 **Can you point out what caused this issue (optional)** Unknown root cause of this issue, may be changed or replaced or missed some core functions between these two versions.

gitea-mirror

2026-05-05 13:01:02 -06:00

closed this issue
added the
WaitingForInfo
label

gitea-mirror commented

2026-05-05 13:01:05 -06:00

Author

Owner

@blizard863 commented on GitHub (Sep 24, 2020):

please show more logs.

@blizard863 commented on GitHub (Sep 24, 2020): please show more logs.

gitea-mirror commented

2026-05-05 13:01:06 -06:00

Author

Owner

@gbh19930406 commented on GitHub (Sep 25, 2020):

Hello, below is the error which shows on FRPC v0.34.0.

work connection write to server error: tls: either ServerName or InsecureSkipVerify must be specified in the tls.Config

@gbh19930406 commented on GitHub (Sep 25, 2020): Hello, below is the error which shows on FRPC v0.34.0. work connection write to server error: tls: either ServerName or InsecureSkipVerify must be specified in the tls.Config

gitea-mirror commented

2026-05-05 13:01:07 -06:00

Author

Owner

@gbh19930406 commented on GitHub (Sep 25, 2020):

Seems I must be specific a Cert and Key in it. There has no default Cert and Key inside of Client 0.34.0, am I right?

@gbh19930406 commented on GitHub (Sep 25, 2020): Seems I must be specific a Cert and Key in it. There has no default Cert and Key inside of Client 0.34.0, am I right?

gitea-mirror commented

2026-05-05 13:01:09 -06:00

Author

Owner

@fatedier commented on GitHub (Sep 25, 2020):

Please follow the issue template to paste your configrues so others can reproduce your problem.

@fatedier commented on GitHub (Sep 25, 2020): Please follow the issue template to paste your configrues so others can reproduce your problem.

gitea-mirror referenced this issue

2026-05-05 14:41:36 -06:00

[PR #1596] [MERGED] v0.31.1, fix bugs #4413