[GH-ISSUE #2554] TLS handshake error #2030

New issue

Closed

opened 2026-05-05 13:18:45 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 13:18:45 -06:00

Owner

Originally created by @yuessir on GitHub (Aug 28, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2554

[REQUIRED] hat version of frp are you using

Version:
0.37. 1

[REQUIRED] What operating system and processor architecture are you using
OS:
B machine win server2019 x64
A machine linux release ubuntu 21 x64
CPU architecture:

[REQUIRED] description of errors

confile

log file

Steps to reproduce the issue

Enable plugin https2https on B machine
Error occurs, remote error: tls: unknown certificate, http: TLS handshake error from xxxx:7000
B機器證書是cloudflare 產生的key與 csr（pem轉crt）
A沒有裝

Supplementary information

Can you guess what caused this issue

Checklist:

[] I included all information required in the sections above
[] I made sure there are no duplicates of this report (Use Search)

Originally created by @yuessir on GitHub (Aug 28, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2554     **[REQUIRED] hat version of frp are you using**  Version: 0.37. 1 **[REQUIRED] What operating system and processor architecture are you using** OS: B machine win server2019 x64 A machine linux release ubuntu 21 x64 CPU architecture: **[REQUIRED] description of errors** **confile**  **log file**  **Steps to reproduce the issue** 1. Enable plugin https2https on B machine 2. 3. Error occurs, remote error: tls: unknown certificate, http: TLS handshake error from xxxx:7000 B機器證書是cloudflare 產生的key與 csr（pem轉crt） A沒有裝 **Supplementary information** **Can you guess what caused this issue** **Checklist**:  - [] I included all information required in the sections above - [] I made sure there are no duplicates of this report [(Use Search)](https://github.com/fatedier/frp/issues?q=is%3Aissue)

gitea-mirror

2026-05-05 13:18:45 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:18:48 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 28, 2021):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Sep 28, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.