github-starred/frp

Fork 0

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

[GH-ISSUE #294] TCP总是连不上 #215

New issue

Closed

opened 2026-05-05 12:00:39 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-05 12:00:39 -06:00

Owner

Originally created by @DL53 on GitHub (Apr 10, 2017).
Original GitHub issue: https://github.com/fatedier/frp/issues/294

[common]
server_addr = 120.*.*.*
server_port = 7000
privilege_token = 12345678
[web01]
privilege_mode = true
type = http
auth_token = 123
local_ip = 192.168.123.1
local_port = 80
use_gzip = true
subdomain = **
[ssh]
type = tcp
auth_token = 123
local_port = 22

frpc.ini配置如上。

[common]
bind_addr = 0.0.0.0
bind_port = 7000
subdomain_host = ****.**
vhost_http_port = 8080
vhost_https_port = 443
dashboard_port = 7500
dashboard_user = admin
dashboard_pwd = admin
log_file = ./frps.log
log_level = info
log_max_days = 3
privilege_mode = true
privilege_token = 12345678
privilege_allow_ports = 2000-3000,3001,3003,4000-50000
max_pool_count = 100
authentication_timeout = 900
[ssh]
type = tcp
auth_token = 12345
listen_port = 22
[web01]
type = http
auth_token = 123
subdomain = **
[web02]
type = http
auth_token =1234
subdomain = ****

frps.ini配置如上，用的是阿里云的服务器。
错误提示如下：

[main.go:109] [I] Start frpc success
2017/04/10 11:15:02 [control.go:202] [E] ProxyName [ssh], start proxy error, ProxyName [ssh], authorization failed
2017/04/10 11:15:02 [control.go:39] [E] ProxyName [ssh], connect to server failed!
2017/04/10 11:15:02 [control.go:206] [I] ProxyName [web01], connect to server [*.*.*.*:7000] success!
2017/04/10 11:15:02 [control.go:220] [I] Start to send heartbeat to frps

Originally created by @DL53 on GitHub (Apr 10, 2017). Original GitHub issue: https://github.com/fatedier/frp/issues/294 ``` [common] server_addr = 120.*.*.* server_port = 7000 privilege_token = 12345678 [web01] privilege_mode = true type = http auth_token = 123 local_ip = 192.168.123.1 local_port = 80 use_gzip = true subdomain = ** [ssh] type = tcp auth_token = 123 local_port = 22 ``` frpc.ini配置如上。 ``` [common] bind_addr = 0.0.0.0 bind_port = 7000 subdomain_host = ****.** vhost_http_port = 8080 vhost_https_port = 443 dashboard_port = 7500 dashboard_user = admin dashboard_pwd = admin log_file = ./frps.log log_level = info log_max_days = 3 privilege_mode = true privilege_token = 12345678 privilege_allow_ports = 2000-3000,3001,3003,4000-50000 max_pool_count = 100 authentication_timeout = 900 [ssh] type = tcp auth_token = 12345 listen_port = 22 [web01] type = http auth_token = 123 subdomain = ** [web02] type = http auth_token =1234 subdomain = **** ``` frps.ini配置如上，用的是阿里云的服务器。错误提示如下： ``` [main.go:109] [I] Start frpc success 2017/04/10 11:15:02 [control.go:202] [E] ProxyName [ssh], start proxy error, ProxyName [ssh], authorization failed 2017/04/10 11:15:02 [control.go:39] [E] ProxyName [ssh], connect to server failed! 2017/04/10 11:15:02 [control.go:206] [I] ProxyName [web01], connect to server [*.*.*.*:7000] success! 2017/04/10 11:15:02 [control.go:220] [I] Start to send heartbeat to frps ```

gitea-mirror closed this issue

2026-05-05 12:00:41 -06:00

gitea-mirror commented

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

Author

Owner

@fatedier commented on GitHub (Apr 10, 2017):

错误提示很明显，auth_token 错误。

@fatedier commented on GitHub (Apr 10, 2017): 错误提示很明显，auth_token 错误。

gitea-mirror commented

2026-05-05 12:00:46 -06:00

Author

Owner

@DL53 commented on GitHub (Apr 10, 2017):

@fatedier 上面的写错了，因为我改过auth_token，不管改成123，还是12345，还是1234，改了好几个都不行。frps和frpc一起改的。而且都重启了。

@DL53 commented on GitHub (Apr 10, 2017): @fatedier 上面的写错了，因为我改过auth_token，不管改成123，还是12345，还是1234，改了好几个都不行。frps和frpc一起改的。而且都重启了。

gitea-mirror commented

2026-05-05 12:00:47 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 10, 2017):

https://github.com/fatedier/frp#communicate-with-your-computer-in-lan-by-ssh

先看文档尝试能否自行解决。

@fatedier commented on GitHub (Apr 10, 2017): https://github.com/fatedier/frp#communicate-with-your-computer-in-lan-by-ssh 先看文档尝试能否自行解决。

gitea-mirror commented

2026-05-05 12:00:48 -06:00

Author

Owner

@DL53 commented on GitHub (Apr 10, 2017):

刚试了下解决了，服务端的 listen_port 应该不应该填22，可以填文档里的6000，还要加上privilege_mode = true, remote_port = 6000。主要是提示错误是authorization failed，一直纠结于auth_token的问题。

@DL53 commented on GitHub (Apr 10, 2017): 刚试了下解决了，服务端的 listen_port 应该不应该填22，可以填文档里的6000，还要加上privilege_mode = true, remote_port = 6000。主要是提示错误是authorization failed，一直纠结于auth_token的问题。

gitea-mirror commented

2026-05-05 12:00:50 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 10, 2017):

你解决的方法是换了一种途径，还是没有抓住问题的重点。

@fatedier commented on GitHub (Apr 10, 2017): 你解决的方法是换了一种途径，还是没有抓住问题的重点。

gitea-mirror commented

2026-05-05 12:00:52 -06:00

Author

Owner

@DL53 commented on GitHub (Apr 10, 2017):

@fatedier 所以问题的重点是什么。。auth token没问题啊。。

@DL53 commented on GitHub (Apr 10, 2017): @fatedier 所以问题的重点是什么。。auth token没问题啊。。

gitea-mirror commented

2026-05-05 12:00:53 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 10, 2017):

比对说明文档的 auth token 配置方式，你的配置是有问题的，所以提示信息没问题。

你后来换了特权模式，就不需要设置 auth token 了，所以规避了这个问题。

@fatedier commented on GitHub (Apr 10, 2017): 比对说明文档的 auth token 配置方式，你的配置是有问题的，所以提示信息没问题。你后来换了特权模式，就不需要设置 auth token 了，所以规避了这个问题。

gitea-mirror commented

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

Author

Owner

@DL53 commented on GitHub (Apr 10, 2017):

好吧，按照说明文档的话，就不能设置不同的auth token了？多个tcp和http的情况下？

@DL53 commented on GitHub (Apr 10, 2017): 好吧，按照说明文档的话，就不能设置不同的auth token了？多个tcp和http的情况下？

gitea-mirror commented

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

Author

Owner

@fatedier commented on GitHub (Apr 10, 2017):

see #213 #212

@fatedier commented on GitHub (Apr 10, 2017): see #213 #212

gitea-mirror commented

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

Author

Owner

@zh-h commented on GitHub (Jul 8, 2017):

我是出现了这种认证错误：
服务端

2017/07/08 12:37:12 [W] [service.go:170] authorization timeout
2017/07/08 12:37:13 [W] [service.go:196] Accept new mux stream error: broken pipe

修改时区后认证正常了，但是还是会出现broken pipe，应该是网络太差了。

@zh-h commented on GitHub (Jul 8, 2017): 我是出现了这种认证错误：服务端 ```bash 2017/07/08 12:37:12 [W] [service.go:170] authorization timeout 2017/07/08 12:37:13 [W] [service.go:196] Accept new mux stream error: broken pipe ``` 修改时区后认证正常了，但是还是会出现broken pipe，应该是网络太差了。

gitea-mirror referenced this issue

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

[PR #215] [MERGED] modified readme.md #4156

gitea-mirror referenced this issue

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

[PR #217] [MERGED] bump version to 0.9.2 #4157