[GH-ISSUE #522] Readme.md is wrong about [secret_ssh], which is [secret_tcp] #401

New issue

Closed

opened 2026-05-05 12:12:56 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 12:12:56 -06:00

Owner

Originally created by @gaozhidf on GitHub (Nov 13, 2017).
Original GitHub issue: https://github.com/fatedier/frp/issues/522

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.
(为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。)

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

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

Configures you used:
secret_tcp

Steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):
readme.md has [secret_ssh], but config example has [secret_tcp]

Can you point out what caused this issue (optional)

Originally created by @gaozhidf on GitHub (Nov 13, 2017). Original GitHub issue: https://github.com/fatedier/frp/issues/522 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. (为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。) 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.13.0 **What operating system and processor architecture are you using (`go env`)?** **Configures you used:** secret_tcp **Steps to reproduce the issue:** 1. 2. 3. **Describe the results you received:** **Describe the results you expected:** **Additional information you deem important (e.g. issue happens only occasionally):** readme.md has [secret_ssh], but config example has [secret_tcp] **Can you point out what caused this issue (optional)**

gitea-mirror closed this issue

2026-05-05 12:12:57 -06:00

gitea-mirror commented

2026-05-05 12:12:59 -06:00

Author

Owner

@gaozhidf commented on GitHub (Nov 13, 2017):

forgot it. it seems you can use [secret_ssh] or [secret_tcp] as proxy name

@gaozhidf commented on GitHub (Nov 13, 2017): forgot it. it seems you can use [secret_ssh] or [secret_tcp] as proxy name

gitea-mirror referenced this issue

2026-05-05 14:37:23 -06:00

[PR #401] [MERGED] merge 0.13 #4190