[GH-ISSUE #441] getsockopt: no route to host #335

New issue

Closed

opened 2026-05-05 12:08:20 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

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

Owner

Originally created by @zhouzhiwen2000 on GitHub (Aug 27, 2017).
Original GitHub issue: https://github.com/fatedier/frp/issues/441

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 0.13.0

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

Configures you used:
[common]
server_addr = 172.104..*
server_port = 7000
privilege_token = ***********
[web]
type = https
local_port = 443
custom_domains = .**,www..**
[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 30022

Steps to reproduce the issue:
1.run frpc for a long time
2.wait till it stops working, restart
3.error message:
2017/08/28 00:02:47 [W] [control.go:121] login to server failed: dial tcp 172.104..:7000: getsockopt: no route to host
dial tcp 172.104..:7000: getsockopt: no route to host
Describe the results you received:
2017/08/28 00:02:47 [W] [control.go:121] login to server failed: dial tcp 172.104..:7000: getsockopt: no route to host
dial tcp 172.104..**:7000: getsockopt: no route to host

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)

Originally created by @zhouzhiwen2000 on GitHub (Aug 27, 2017). Original GitHub issue: https://github.com/fatedier/frp/issues/441 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 0.13.0 **What operating system and processor architecture are you using (`go env`)?** linux arm **Configures you used:** [common] server_addr = 172.104.**.*** server_port = 7000 privilege_token = *********** [web] type = https local_port = 443 custom_domains = ****.**,www.****.** [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 30022 **Steps to reproduce the issue:** 1.run frpc for a long time 2.wait till it stops working, restart 3.error message: 2017/08/28 00:02:47 [W] [control.go:121] login to server failed: dial tcp 172.104.**.***:7000: getsockopt: no route to host dial tcp 172.104.**.***:7000: getsockopt: no route to host **Describe the results you received:** 2017/08/28 00:02:47 [W] [control.go:121] login to server failed: dial tcp 172.104.**.***:7000: getsockopt: no route to host dial tcp 172.104.**.***:7000: getsockopt: no route to host **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)**