[GH-ISSUE #758] 18.0版不能访问secret connect #593

New issue

Closed

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

gitea-mirror commented

2026-05-05 12:23:08 -06:00

Owner

Originally created by @xhhgithub on GitHub (May 10, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/758

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)?
./frpc -v 18.0 or ./frps -v 18.0

What operating system and processor architecture are you using (go env)?
windows 10 client, server： debian 9

Configures you used:
configures worked perfect in v 16.0

Steps to reproduce the issue:
1.server frps start
2.client frpc start, and secret serve started
3.another pc frpc started, config ok, but cant visit secret serve

Describe the results you received:
[W] [visitor.go:140] [your_name.secret_tscxhhpc_visitor] start new visitor connection error: custom listener for [secret_tscxhhpc] doesn't exist
this if from frpc.log
Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):
below from frps.log

2018/05/10 03:48:04 [I] [proxy.go:118] [ec938816ba32d33e] [your_name.secret_tscxdell] listener is closed
2018/05/10 03:53:47 [I] [service.go:262] client login info: ip [182.18.16.75:52189] version [0.18.0] hostname [] os [windows] arch [amd64]
2018/05/10 03:53:47 [W] [service.go:207] authorization failed
2018/05/10 03:53:55 [I] [service.go:262] client login info: ip [182.18.16.75:51094] version [0.18.0] hostname [] os [windows] arch [amd64]
2018/05/10 03:53:55 [W] [service.go:207] authorization failed
2018/05/10 03:54:27 [W] [service.go:247] Accept new mux stream error: keepalive timeout
2018/05/10 03:54:35 [W] [service.go:247] Accept new mux stream error: keepalive timeout

Can you point out what caused this issue (optional)
18.0 update? what changed? yamux?

Originally created by @xhhgithub on GitHub (May 10, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/758 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)?** ./frpc -v 18.0 or ./frps -v 18.0 **What operating system and processor architecture are you using (`go env`)?** windows 10 client, server： debian 9 **Configures you used:** configures worked perfect in v 16.0 **Steps to reproduce the issue:** 1.server frps start 2.client frpc start, and secret serve started 3.another pc frpc started, config ok, but cant visit secret serve **Describe the results you received:** [W] [visitor.go:140] [your_name.secret_tscxhhpc_visitor] start new visitor connection error: custom listener for [secret_tscxhhpc] doesn't exist this if from frpc.log **Describe the results you expected:** **Additional information you deem important (e.g. issue happens only occasionally):** below from frps.log 2018/05/10 03:48:04 [I] [proxy.go:118] [ec938816ba32d33e] [your_name.secret_tscxdell] listener is closed 2018/05/10 03:53:47 [I] [service.go:262] client login info: ip [182.18.16.75:52189] version [0.18.0] hostname [] os [windows] arch [amd64] 2018/05/10 03:53:47 [W] [service.go:207] authorization failed 2018/05/10 03:53:55 [I] [service.go:262] client login info: ip [182.18.16.75:51094] version [0.18.0] hostname [] os [windows] arch [amd64] 2018/05/10 03:53:55 [W] [service.go:207] authorization failed 2018/05/10 03:54:27 [W] [service.go:247] Accept new mux stream error: keepalive timeout 2018/05/10 03:54:35 [W] [service.go:247] Accept new mux stream error: keepalive timeout **Can you point out what caused this issue (optional)** 18.0 update? what changed? yamux?