[GH-ISSUE #141] frps invalid character '\x16' #85

Closed
opened 2026-05-05 11:43:40 -06:00 by gitea-mirror · 10 comments
Owner

Originally created by @hanxi on GitHub (Oct 20, 2016).
Original GitHub issue: https://github.com/fatedier/frp/issues/141

2016/10/20 17:57:10 [control.go:67] [W] Parse msg from frpc error: invalid character '\x16' looking for beginning of value : !KUtBXJzg):o
                                                                                                                                         /+0,

v0ҧnHS1mi/+0,:57:40 [control.go:67] [W] Parse msg from frpc error: invalid character '\x16' looking for beginning of value :

2016/10/20 17:58:09 [control.go:67] [W] Parse msg from frpc error: invalid character '\x16' looking for beginning of value : GN%J6v3=s/+0,

经常出现这个错误。

Originally created by @hanxi on GitHub (Oct 20, 2016). Original GitHub issue: https://github.com/fatedier/frp/issues/141 ``` 2016/10/20 17:57:10 [control.go:67] [W] Parse msg from frpc error: invalid character '\x16' looking for beginning of value : !KUtBXJzg):o /+0, v0ҧnHS1mi/+0,:57:40 [control.go:67] [W] Parse msg from frpc error: invalid character '\x16' looking for beginning of value : 2016/10/20 17:58:09 [control.go:67] [W] Parse msg from frpc error: invalid character '\x16' looking for beginning of value : GN%J6v3=s/+0, ``` 经常出现这个错误。
gitea-mirror 2026-05-05 11:43:40 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@cnluzhang commented on GitHub (Oct 20, 2016):

我遇到的问题是 invalid character 'G' looking for beginning of value : GET / HTTP/1.1

<!-- gh-comment-id:255072581 --> @cnluzhang commented on GitHub (Oct 20, 2016): 我遇到的问题是 invalid character 'G' looking for beginning of value : GET / HTTP/1.1
Author
Owner

@fatedier commented on GitHub (Oct 20, 2016):

能贴一下相关的配置信息吗?

<!-- gh-comment-id:255108007 --> @fatedier commented on GitHub (Oct 20, 2016): 能贴一下相关的配置信息吗?
Author
Owner

@fatedier commented on GitHub (Oct 20, 2016):

@cnluzhang 你的有可能是端口被扫到了,对 frps 的服务端口发送了一个 http 的请求,内容不符合交互协议格式,所以解析出错。

<!-- gh-comment-id:255159788 --> @fatedier commented on GitHub (Oct 20, 2016): @cnluzhang 你的有可能是端口被扫到了,对 frps 的服务端口发送了一个 http 的请求,内容不符合交互协议格式,所以解析出错。
Author
Owner

@hanxi commented on GitHub (Oct 25, 2016):

frps.ini (10.12.1.224)

[common]
bind_addr = 10.12.1.224
bind_port = 9022
vhost_http_port = 9021
dashboard_port = 7500
log_file = ./frps.log
log_level = info
log_max_days = 3
privilege_mode = true
privilege_token = 0x12345678

frpc.ini (10.12.1.224)

[common]
server_addr = 10.12.1.224
server_port = 9022
log_file = ./frpc.log
log_level = info
log_max_days = 3
privilege_token = 0x12345678

[s1]
privilege_mode = true
type = http
local_ip = 10.12.1.224
local_port = 9001
custom_domains = s1.server.tlx
use_encryption = false
use_gzip = false

frpc.ini (10.5.2.235)

[common]
server_addr = 10.5.2.242 # 端口映射到 10.12.1.224
server_port = 9022
log_file = ./frpc.log
log_level = info
log_max_days = 3
privilege_token = 0x12345678

[login]
privilege_mode = true
type = http
local_ip = 10.5.2.235
local_port = 8001
custom_domains = login.server.tlx
use_encryption = false
use_gzip = false

虽然有上面说的报错,但是能使用。有一个问题就是 10.12.1.224:9001 收到的包有可能是被打乱,数据末尾附带着部分 10.12.1.22410.5.2.235:8001 发的数据。
例如:

10.12.1.224 每秒发送 {"data":"nihao"} 到 10.5.2.235:8001
10.5.2.235 每秒发送 {"test":-1} 到 10.12.1.224:9001
此时 10.12.1.224:9001 收到的数据有概率是 {"test":-1}hao"}

之前我是用ngrok搭建的,没有存在这个问题。所以就来这里提issue了,我不会 Go, 就没去看实现了,有可能是因为用到了同一个Buffer。

<!-- gh-comment-id:255914028 --> @hanxi commented on GitHub (Oct 25, 2016): frps.ini (10.12.1.224) ``` [common] bind_addr = 10.12.1.224 bind_port = 9022 vhost_http_port = 9021 dashboard_port = 7500 log_file = ./frps.log log_level = info log_max_days = 3 privilege_mode = true privilege_token = 0x12345678 ``` frpc.ini (10.12.1.224) ``` [common] server_addr = 10.12.1.224 server_port = 9022 log_file = ./frpc.log log_level = info log_max_days = 3 privilege_token = 0x12345678 [s1] privilege_mode = true type = http local_ip = 10.12.1.224 local_port = 9001 custom_domains = s1.server.tlx use_encryption = false use_gzip = false ``` frpc.ini (10.5.2.235) ``` [common] server_addr = 10.5.2.242 # 端口映射到 10.12.1.224 server_port = 9022 log_file = ./frpc.log log_level = info log_max_days = 3 privilege_token = 0x12345678 [login] privilege_mode = true type = http local_ip = 10.5.2.235 local_port = 8001 custom_domains = login.server.tlx use_encryption = false use_gzip = false ``` 虽然有上面说的报错,但是能使用。有一个问题就是 `10.12.1.224:9001` 收到的包有可能是被打乱,数据末尾附带着部分 `10.12.1.224` 往 `10.5.2.235:8001` 发的数据。 例如: `10.12.1.224` 每秒发送 {"data":"nihao"} 到 `10.5.2.235:8001` `10.5.2.235` 每秒发送 {"test":-1} 到 `10.12.1.224:9001` 此时 `10.12.1.224:9001` 收到的数据有概率是 {"test":-1}hao"} 之前我是用ngrok搭建的,没有存在这个问题。所以就来这里提issue了,我不会 Go, 就没去看实现了,有可能是因为用到了同一个Buffer。
Author
Owner

@mmsoon commented on GitHub (Dec 16, 2016):

遇到类似的问题,http包转发不完整,某一个js文件请求时经常在固定的位置断开,后面的部分就没有了。

<!-- gh-comment-id:267513159 --> @mmsoon commented on GitHub (Dec 16, 2016): 遇到类似的问题,http包转发不完整,某一个js文件请求时经常在固定的位置断开,后面的部分就没有了。
Author
Owner

@fatedier commented on GitHub (Dec 16, 2016):

@SongJoey 能否提供可以稳定复现的测试代码和资源文件?

<!-- gh-comment-id:267513326 --> @fatedier commented on GitHub (Dec 16, 2016): @SongJoey 能否提供可以稳定复现的测试代码和资源文件?
Author
Owner

@mmsoon commented on GitHub (Dec 16, 2016):

没办法稳定复现。经常出现在我改动这个文件之后,会有一段时间,不管怎么重复请求都不行,但过一会儿又好了。
我再试试,如果发现规律的话我再报过来。

<!-- gh-comment-id:267514399 --> @mmsoon commented on GitHub (Dec 16, 2016): 没办法稳定复现。经常出现在我改动这个文件之后,会有一段时间,不管怎么重复请求都不行,但过一会儿又好了。 我再试试,如果发现规律的话我再报过来。
Author
Owner

@fatedier commented on GitHub (Dec 16, 2016):

@SongJoey 好的,感谢反馈,如果能够定位到问题的话,我会尽快修复,不然我也无法判断是什么原因引起的。

<!-- gh-comment-id:267514689 --> @fatedier commented on GitHub (Dec 16, 2016): @SongJoey 好的,感谢反馈,如果能够定位到问题的话,我会尽快修复,不然我也无法判断是什么原因引起的。
Author
Owner

@fatedier commented on GitHub (Dec 28, 2016):

invalid character 本地偶然复现了这个问题,暂时没有定位到原因。

<!-- gh-comment-id:269423330 --> @fatedier commented on GitHub (Dec 28, 2016): invalid character 本地偶然复现了这个问题,暂时没有定位到原因。
Author
Owner

@fatedier commented on GitHub (May 21, 2017):

v0.10.0 版本更改了这部分的逻辑。

<!-- gh-comment-id:302927572 --> @fatedier commented on GitHub (May 21, 2017): v0.10.0 版本更改了这部分的逻辑。
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#85
No description provided.