github-starred/frp

Fork 0

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

[GH-ISSUE #1477] 两台frpc连接一个frps，都显示成功，但是一台无法连接，能提供排查问题的思路吗？ #1163

New issue

Closed

opened 2026-05-05 12:44:54 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 12:44:54 -06:00

Owner

Originally created by @chenqiuyuan on GitHub (Oct 22, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1477

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 将会直接关闭。)
(请不要在 issue 评论中出现无意义的加1，我也是 等内容，将会被直接删除。)
(由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。)

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

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

Configures you used:
frpc1 和frpc2一模一样（除了[ssh]和端口）
[common]
server_addr = frps ip
server_port = 5443
[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 8886

Steps to reproduce the issue:

启动frps
在两台客户机分别启动frpc

Describe the results you received:
都显示成功，但是先启动的能穿透，后启动的去连接直接就是time out。

Describe the results you expected:
都能成功。

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

Can you point out what caused this issue (optional)
使用后一台相同配置连了其他frps，发现能够成功。
主要难点在于都显示成功[start proxy success]，但结果只有一台能用，不知道错误发生在哪里。

Originally created by @chenqiuyuan on GitHub (Oct 22, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1477 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 将会直接关闭。) (请不要在 issue 评论中出现无意义的 **加1**，**我也是** 等内容，将会被直接删除。) (由于个人精力有限，和系统环境，网络环境等相关的求助问题请转至其他论坛或社交平台。) 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.27.0 **What operating system and processor architecture are you using (`go env`)?** ubuntu **Configures you used:** frpc1 和frpc2一模一样（除了[ssh]和端口） [common] server_addr = frps ip server_port = 5443 [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 8886 **Steps to reproduce the issue:** 1. 启动frps 2. 在两台客户机分别启动frpc 3. **Describe the results you received:** 都显示成功，但是先启动的能穿透，后启动的去连接直接就是time out。 **Describe the results you expected:** 都能成功。 **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)** 使用后一台相同配置连了其他frps，发现能够成功。主要难点在于都显示成功[start proxy success]，但结果只有一台能用，不知道错误发生在哪里。

gitea-mirror closed this issue

2026-05-05 12:44:55 -06:00

gitea-mirror commented

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

Author

Owner

@littlesum commented on GitHub (Oct 23, 2019):

你看下日志啊开日志了么？

@littlesum commented on GitHub (Oct 23, 2019): 你看下日志啊开日志了么？

gitea-mirror commented

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

Author

Owner

@chenqiuyuan commented on GitHub (Oct 23, 2019):

你看下日志啊开日志了么？

日志里只显示连接成功。

但是我搞定了，是阿里云把端口拦截了，开放了之后就好了。我觉得这个问题应该写到readme里面作为提示，因为如果不知道拦截这回事，日志里完全不会体现。

@chenqiuyuan commented on GitHub (Oct 23, 2019): > > > 你看下日志啊开日志了么？日志里只显示连接成功。但是我搞定了，是阿里云把端口拦截了，开放了之后就好了。我觉得这个问题应该写到readme里面作为提示，因为如果不知道拦截这回事，日志里完全不会体现。

gitea-mirror commented

2026-05-05 12:44:58 -06:00

Author

Owner

@douxiaotian commented on GitHub (Oct 23, 2019):

？

Fallaway notifications@github.com于2019年10月23日周三上午12:43写道：

Closed #1477 https://github.com/fatedier/frp/issues/1477.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fatedier/frp/issues/1477?email_source=notifications&email_token=ABDJXLAEXAX5GHGS6LP4FHDQP7JAFA5CNFSM4JDPLSX2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUMG5SIA#event-2735593760,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDJXLCU2KLJYMDKPJIJDQDQP7JAFANCNFSM4JDPLSXQ
.

--
*Jason Dou *
jasondou.org

@douxiaotian commented on GitHub (Oct 23, 2019): ？ Fallaway <notifications@github.com>于2019年10月23日周三上午12:43写道： > Closed #1477 <https://github.com/fatedier/frp/issues/1477>. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/fatedier/frp/issues/1477?email_source=notifications&email_token=ABDJXLAEXAX5GHGS6LP4FHDQP7JAFA5CNFSM4JDPLSX2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUMG5SIA#event-2735593760>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABDJXLCU2KLJYMDKPJIJDQDQP7JAFANCNFSM4JDPLSXQ> > . > -- *Jason Dou * jasondou.org

gitea-mirror commented

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

Author

Owner

@wyyl1 commented on GitHub (May 9, 2020):

你看下日志啊开日志了么？

日志里只显示连接成功。

但是我搞定了，是阿里云把端口拦截了，开放了之后就好了。我觉得这个问题应该写到readme里面作为提示，因为如果不知道拦截这回事，日志里完全不会体现。

真的是阿里云把端口拦截了！之前以为他只拦截3306端口，原来什么都拦截！

@wyyl1 commented on GitHub (May 9, 2020): > > 你看下日志啊开日志了么？ > > 日志里只显示连接成功。 > > 但是我搞定了，是阿里云把端口拦截了，开放了之后就好了。我觉得这个问题应该写到readme里面作为提示，因为如果不知道拦截这回事，日志里完全不会体现。真的是阿里云把端口拦截了！之前以为他只拦截3306端口，原来什么都拦截！