github-starred/frp
2
0
Fork 0
mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00
Code Issues 40 Projects Packages Wiki Activity Actions 1

[GH-ISSUE #637] 客户端网络关闭，而服务端不能自动关闭连接 #497

New issue
Closed
opened 2026-05-05 12:19:28 -06:00 by gitea-mirror · 3 comments
gitea-mirror commented 2026-05-05 12:19:28 -06:00
Owner
Copy link

Originally created by @m2276699 on GitHub (Feb 17, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/637

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

What operating system and processor architecture are you using (go env)?
Server：Ubuntu 16.04.3，Client：Win10

Configures you used:
frps.ini
[common]
bind_addr = 0.0.0.0
bind_port = 7000
bind_udp_port = 7880
kcp_bind_port = 7000
vhost_http_port = 80
vhost_https_port = 443
privilege_token = 123456
max_pool_count = 5
max_ports_per_client = 0
authentication_timeout = 900
tcp_mux = true

frpc.ini
[common]
server_addr = x.123.com
server_port = 7000
tcp_mux = true
privilege_token = 123456
protocol = kcp
tcp_mux = true
log_file = ./frpc.log
log_level = trace
log_max_days = 3
pool_count = 5

[git_web]
type = http
local_ip = 127.0.0.1
local_port = 80
use_encryption = true
use_compression = true
custom_domains = xx.123.com

Steps to reproduce the issue:
1.分别启动FRPS、FRPC
2.用git push 300M左右的源码到FRPC上的git server
3.进度大概80%出现一次连接断开，等待20分钟无法重连
4.20分钟后重启FRPC提示：[git_web] start error: router config conflict

Describe the results you received:
[git_web] start error: router config conflict

Describe the results you expected:
期望能正常打开frpc，或frpc能成功自动重连

Additional information you deem important (e.g. issue happens only occasionally):
2018/02/18 00:00:04 [I] [proxy.go:85] [b1b773b1c46f7dd6] [git_web] get a new work connection: [x.x.x.x:21439]
2018/02/18 00:00:06 [I] [proxy.go:85] [b1b773b1c46f7dd6] [git_web] get a new work connection: [x.x.x.x:21439]
2018/02/18 00:00:07 [I] [proxy.go:85] [b1b773b1c46f7dd6] [git_web] get a new work connection: [x.x.x.x:21439]
2018/02/18 00:37:20 [W] [control.go:304] [b1b773b1c46f7dd6] heartbeat timeout
2018/02/18 00:37:20 [I] [control.go:213] [b1b773b1c46f7dd6] control writer is closing
2018/02/18 00:37:20 [W] [control.go:241] [b1b773b1c46f7dd6] read error: broken pipe
2018/02/18 02:47:50 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:01 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:01 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:02 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:02 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:03 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:03 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:04 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:05 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:05 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:06 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:06 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:07 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:07 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:08 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:08 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:09 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:09 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:10 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:10 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:11 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:11 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 03:18:12 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 05:04:21 [W] [vhost.go:134] get hostname from http/https request error: EOF
2018/02/18 05:04:21 [W] [vhost.go:134] get hostname from http/https request error: Unknow error
2018/02/18 05:04:21 [W] [vhost.go:134] get hostname from http/https request error: Unknow error
2018/02/18 05:38:42 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 05:38:43 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 05:38:43 [W] [newhttp.go:189] http: proxy error: no such domain
2018/02/18 05:38:43 [W] [newhttp.go:189] http: proxy error: no such domain

2018/02/18 07:56:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict
2018/02/18 07:56:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success
2018/02/18 07:57:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict
2018/02/18 07:57:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success
2018/02/18 07:58:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict
2018/02/18 07:58:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success
2018/02/18 07:59:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict
2018/02/18 07:59:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success
2018/02/18 08:00:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict

Can you point out what caused this issue (optional)
个人感觉FRPS没有成功关闭已断开的FRPC连接，导致FRPC重连出现router config conflict的提示

Originally created by @m2276699 on GitHub (Feb 17, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/637 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.16.0 **What operating system and processor architecture are you using (`go env`)?** Server：Ubuntu 16.04.3，Client：Win10 **Configures you used:** frps.ini [common] bind_addr = 0.0.0.0 bind_port = 7000 bind_udp_port = 7880 kcp_bind_port = 7000 vhost_http_port = 80 vhost_https_port = 443 privilege_token = 123456 max_pool_count = 5 max_ports_per_client = 0 authentication_timeout = 900 tcp_mux = true frpc.ini [common] server_addr = x.123.com server_port = 7000 tcp_mux = true privilege_token = 123456 protocol = kcp tcp_mux = true log_file = ./frpc.log log_level = trace log_max_days = 3 pool_count = 5 [git_web] type = http local_ip = 127.0.0.1 local_port = 80 use_encryption = true use_compression = true custom_domains = xx.123.com **Steps to reproduce the issue:** 1.分别启动FRPS、FRPC 2.用git push 300M左右的源码到FRPC上的git server 3.进度大概80%出现一次连接断开，等待20分钟无法重连 4.20分钟后重启FRPC提示：[git_web] start error: router config conflict **Describe the results you received:** [git_web] start error: router config conflict **Describe the results you expected:** 期望能正常打开frpc，或frpc能成功自动重连 **Additional information you deem important (e.g. issue happens only occasionally):** 2018/02/18 00:00:04 [I] [proxy.go:85] [b1b773b1c46f7dd6] [git_web] get a new work connection: [x.x.x.x:21439] 2018/02/18 00:00:06 [I] [proxy.go:85] [b1b773b1c46f7dd6] [git_web] get a new work connection: [x.x.x.x:21439] 2018/02/18 00:00:07 [I] [proxy.go:85] [b1b773b1c46f7dd6] [git_web] get a new work connection: [x.x.x.x:21439] 2018/02/18 00:37:20 [W] [control.go:304] [b1b773b1c46f7dd6] heartbeat timeout 2018/02/18 00:37:20 [I] [control.go:213] [b1b773b1c46f7dd6] control writer is closing 2018/02/18 00:37:20 [W] [control.go:241] [b1b773b1c46f7dd6] read error: broken pipe 2018/02/18 02:47:50 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:01 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:01 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:02 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:02 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:03 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:03 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:04 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:05 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:05 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:06 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:06 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:07 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:07 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:08 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:08 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:09 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:09 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:10 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:10 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:11 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:11 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 03:18:12 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 05:04:21 [W] [vhost.go:134] get hostname from http/https request error: EOF 2018/02/18 05:04:21 [W] [vhost.go:134] get hostname from http/https request error: Unknow error 2018/02/18 05:04:21 [W] [vhost.go:134] get hostname from http/https request error: Unknow error 2018/02/18 05:38:42 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 05:38:43 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 05:38:43 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 05:38:43 [W] [newhttp.go:189] http: proxy error: no such domain 2018/02/18 07:56:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict 2018/02/18 07:56:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success 2018/02/18 07:57:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict 2018/02/18 07:57:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success 2018/02/18 07:58:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict 2018/02/18 07:58:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success 2018/02/18 07:59:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict 2018/02/18 07:59:31 [I] [control.go:330] [31e19d14e2033f10] close proxy [git_web] success 2018/02/18 08:00:31 [W] [control.go:321] [31e19d14e2033f10] new proxy [git_web] error: router config conflict **Can you point out what caused this issue (optional)** 个人感觉FRPS没有成功关闭已断开的FRPC连接，导致FRPC重连出现router config conflict的提示
gitea-mirror commented 2026-05-05 12:19:31 -06:00
Author
Owner
Copy link

@kavid commented on GitHub (Apr 3, 2018):

楼主最后解决了这个吗》？》？

<!-- gh-comment-id:378239313 --> @kavid commented on GitHub (Apr 3, 2018): 楼主最后解决了这个吗》？》？
gitea-mirror commented 2026-05-05 12:19:32 -06:00
Author
Owner
Copy link

@xingdaos commented on GitHub (Aug 2, 2018):

我部署的时候也遇到了类似的情况：

http: proxy error: no such domain #这是客户端配置的域名有误或没有得到正确解析，建议确认域名正确无误
error: router config conflict #这个是因为有另一个配置了相同远程端口的客户端正在运行，冲突了，建议关掉相应的一个客户端
<!-- gh-comment-id:409949651 --> @xingdaos commented on GitHub (Aug 2, 2018): 我部署的时候也遇到了类似的情况： ``` http: proxy error: no such domain #这是客户端配置的域名有误或没有得到正确解析，建议确认域名正确无误 error: router config conflict #这个是因为有另一个配置了相同远程端口的客户端正在运行，冲突了，建议关掉相应的一个客户端 ```
gitea-mirror commented 2026-05-05 12:19:32 -06:00
Author
Owner
Copy link

@vpei commented on GitHub (Oct 15, 2022):

这个问题解决了吗？

<!-- gh-comment-id:1279772008 --> @vpei commented on GitHub (Oct 15, 2022): 这个问题解决了吗？
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
new
master
copilot/review-pull-request-5198
v0.68.1
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.1
v0.62.0
v0.61.2
v0.61.1
v0.61.0
v0.60.0
v0.59.0
v0.58.1
v0.58.0
v0.57.0
v0.56.0
v0.55.1
v0.55.0
v0.54.0
v0.53.2
v0.53.1
v0.53.0
v0.52.3
v0.52.2
v0.52.1
v0.52.0
v0.51.3
v0.51.2
v0.51.1
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.1
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.1
v0.39.0
v0.38.0
v0.37.1
v0.37.0
v0.36.2
v0.36.1
v0.36.0
v0.35.1
v0.35.0
v0.34.3
v0.34.2
v0.34.1
v0.34.0
v0.33.0
v0.32.1
v0.32.0
v0.31.2
v0.31.1
v0.31.0
v0.30.0
v0.29.1
v0.29.0
v0.28.2
v0.28.1
v0.28.0
v0.27.1
v0.27.0
v0.26.0
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.1
v0.24.0
v0.23.3
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.1
v0.19.0
v0.18.0
v0.17.0
v0.16.1
v0.16.0
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.1
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
In Progress

   
WIP

   
WaitingForInfo

   
bug

   
doc

   
duplicate

   
easy

   
enhancement

   
future

   
help wanted

   
invalid

   
lifecycle/stale

   
need-issue-template

   
need-usage-help

   
no plan

   
proposal

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
todo
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#497
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?