github-starred/frp

Fork 0

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

[GH-ISSUE #1986] login to server failed: EOF #1580

New issue

Closed

opened 2026-05-05 13:00:09 -06:00 by gitea-mirror · 14 comments

gitea-mirror commented

2026-05-05 13:00:09 -06:00

Owner

Originally created by @xueyuanl on GitHub (Sep 16, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/1986

What version of frp are you using (./frpc -v or ./frps -v)?
0.33.0/ 0.33.0

What operating system and processor architecture are you using (go env)?
service: centOS x86_64(VPS on linode in Japan)
client: macOS i386 (macbook pro catalina, zsh)

Configures you used:
service: one VPS server on linode, base in Japan.

[common]
bind_port = 7000

client: macbook in china mainland 电信 (actually I still tried on a raspberry pi with same comfig)

[common]
server_addr = x.x.x.x
server_port = 7000

[ssh]
type = tcp
local_ip = 127.0.0.1
local_post = 22
remote_port = 6000

Steps to reproduce the issue:

config as above
2.run ./frps -c frps.ini on server side
3.run .frpc -c frpc.ini on client side

Describe the results you received:

[W] [service.go:101] login to server failed: EOF

Describe the results you expected:
run success

Additional information you deem important (e.g. issue happens only occasionally):
I tried it on my private LAN, this can work. So obviously, this is not the problem of the software itself.

telnet result:

$: telnet x.x.x.x 7000
Trying x.x.x.x
Connected to x
Escape character is '^]'.
Connection closed by foreign host.

And I just search on google and baidu, found lots of solution but did not work for me,
for example:
记一次frp的被阻断的问题
 issue 1249 frpc提示login to server failed: EOF
issue 1836 疑似被局域网禁用连接

or some solution did not work because of the older version like this,
issue 810
frp启动报错“[W] [control.go:113] login to server failed: EOF”

Can you point out what caused this issue (optional)
我个人觉得和国内的防火墙有关，希望有类似问题的同学给点意见。
I suspect that this problem is related to the china GFW.
Yes, this is not an issue, but I still hope someone can help me on this.

Thanks

Originally created by @xueyuanl on GitHub (Sep 16, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/1986 **What version of frp are you using (./frpc -v or ./frps -v)?** 0.33.0/ 0.33.0 **What operating system and processor architecture are you using (`go env`)?** service: centOS x86_64(VPS on linode in Japan) client: macOS i386 (macbook pro catalina, zsh) **Configures you used:** service: one VPS server on linode, base in Japan. ``` [common] bind_port = 7000 ``` client: macbook in china mainland 电信 (actually I still tried on a raspberry pi with same comfig) ``` [common] server_addr = x.x.x.x server_port = 7000 [ssh] type = tcp local_ip = 127.0.0.1 local_post = 22 remote_port = 6000 ``` **Steps to reproduce the issue:** 1. config as above 2.run `./frps -c frps.ini `on server side 3.run `.frpc -c frpc.ini `on client side **Describe the results you received:** ``` [W] [service.go:101] login to server failed: EOF ``` **Describe the results you expected:** run success **Additional information you deem important (e.g. issue happens only occasionally):** `I tried it on my private LAN, this can work. So obviously, this is not the problem of the software itself.` telnet result: ``` $: telnet x.x.x.x 7000 Trying x.x.x.x Connected to x Escape character is '^]'. Connection closed by foreign host. ``` And I just search on google and baidu, found lots of solution but did not work for me, for example: [记一次frp的被阻断的问题](https://blog.phpgao.com/frp_tcp_reset.html) [issue 1249 frpc提示login to server failed: EOF](https://github.com/fatedier/frp/issues/1249) [issue 1836 疑似被局域网禁用连接](https://github.com/fatedier/frp/issues/1836) or some solution did not work because of the older version like this, [issue 810](https://github.com/fatedier/frp/issues/810) [frp启动报错“[W] [control.go:113] login to server failed: EOF”](https://www.codeleading.com/article/53751252444/) **Can you point out what caused this issue (optional)** 我个人觉得和国内的防火墙有关，希望有类似问题的同学给点意见。 I suspect that this problem is related to the china GFW. Yes, this is not an issue, but I still hope someone can help me on this. Thanks

gitea-mirror

2026-05-05 13:00:09 -06:00

closed this issue
added the
lifecycle/stale

WaitingForInfo
labels

gitea-mirror commented

2026-05-05 13:00:13 -06:00

Author

Owner

@blizard863 commented on GitHub (Sep 16, 2020):

可以尝试开启下 kcp看下效果。

@blizard863 commented on GitHub (Sep 16, 2020): 可以尝试开启下 kcp看下效果。

gitea-mirror commented

2026-05-05 13:00:14 -06:00

Author

Owner

@blizard863 commented on GitHub (Sep 16, 2020):

或者开下 tls 试试。后续应该会支持自定义的 tls config https://github.com/fatedier/frp/pull/1974

@blizard863 commented on GitHub (Sep 16, 2020): 或者开下 tls 试试。后续应该会支持自定义的 tls config https://github.com/fatedier/frp/pull/1974

gitea-mirror commented

2026-05-05 13:00:14 -06:00

Author

Owner

@xueyuanl commented on GitHub (Sep 16, 2020):

可以尝试开启下 kcp看下效果。

server side:

[common]
bind_port = 7000
kcp_bind_port = 7000

client side:

[common]
server_addr = x.x.x.x
server_port = 7000
protocol = kcp

[ssh]
type = tcp
local_ip = 127.0.0.1
local_post = 22
remote_port = 6000

error 报错：
[service.go:101] login to server failed: i/o deadline reached

但局域网测试依然可以。

@xueyuanl commented on GitHub (Sep 16, 2020): > 可以尝试开启下 kcp看下效果。 server side: ``` [common] bind_port = 7000 kcp_bind_port = 7000 ``` client side: ``` [common] server_addr = x.x.x.x server_port = 7000 protocol = kcp [ssh] type = tcp local_ip = 127.0.0.1 local_post = 22 remote_port = 6000 ``` error 报错： `[service.go:101] login to server failed: i/o deadline reached` 但局域网测试依然可以。

gitea-mirror commented

2026-05-05 13:00:15 -06:00

Author

Owner

@xueyuanl commented on GitHub (Sep 16, 2020):

或者开下 tls 试试。后续应该会支持自定义的 tls config #1974

add tls_enable = true in client's (or in both server and client side) common section, still does not work.

get error: [service.go:101] login to server failed: session shutdown

@xueyuanl commented on GitHub (Sep 16, 2020): > 或者开下 tls 试试。后续应该会支持自定义的 tls config #1974 add `tls_enable = true` in client's (or in both server and client side) `common` section, still does not work. get error: `[service.go:101] login to server failed: session shutdown`

gitea-mirror commented

2026-05-05 13:00:16 -06:00

Author

Owner

@blizard863 commented on GitHub (Sep 16, 2020):

frpc 和 frps 的日志可以多提供一点。

@blizard863 commented on GitHub (Sep 16, 2020): frpc 和 frps 的日志可以多提供一点。

gitea-mirror commented

2026-05-05 13:00:17 -06:00

Author

Owner

@jaredyam commented on GitHub (Sep 23, 2020):

一模一样的问题，请问解决了吗？

@jaredyam commented on GitHub (Sep 23, 2020): 一模一样的问题，请问解决了吗？

gitea-mirror commented

2026-05-05 13:00:18 -06:00

Author

Owner

@xueyuanl commented on GitHub (Sep 23, 2020):

一模一样的问题，请问解决了吗？

还没有解决 : (
still not figure it out

@xueyuanl commented on GitHub (Sep 23, 2020): > 一模一样的问题，请问解决了吗？还没有解决 : ( still not figure it out

gitea-mirror commented

2026-05-05 13:00:18 -06:00

Author

Owner

@mouyong commented on GitHub (Sep 24, 2020):

注释掉 server 端的插件，然后用 frps_full.ini 启动，客户端就可以连接了。

@xueyuanl @jaredyam

@mouyong commented on GitHub (Sep 24, 2020): 注释掉 server 端的插件，然后用 frps_full.ini 启动，客户端就可以连接了。 @xueyuanl @jaredyam

gitea-mirror commented

2026-05-05 13:00:19 -06:00

Author

Owner

@trulyliu commented on GitHub (Oct 3, 2020):

authentication_method = token

注意server端的这个选项

@trulyliu commented on GitHub (Oct 3, 2020): `authentication_method = token` 注意server端的这个选项

gitea-mirror commented

2026-05-05 13:00:20 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 13, 2020):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Dec 13, 2020): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 13:00:21 -06:00

Author

Owner

@progerchai commented on GitHub (Jun 18, 2021):

authentication_method = token

注意server端的这个选项

在frps_full.ini 中这个默认是开启的，和楼上的相同没有解决

@progerchai commented on GitHub (Jun 18, 2021): > `authentication_method = token` > > 注意server端的这个选项在frps_full.ini 中这个默认是开启的，和楼上的相同没有解决

gitea-mirror commented

2026-05-05 13:00:22 -06:00

Author

Owner

@jackxuexue commented on GitHub (Dec 6, 2021):

亲测：frpc.ini 加上 tls_enable = true 即可
`[common]
server_addr =xxxxxxx
server_port = 7000
tls_enable = true

[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 6000`
版本：frp_0.38.0_linux_amd64

@jackxuexue commented on GitHub (Dec 6, 2021): 亲测：frpc.ini 加上 tls_enable = true 即可 `[common] server_addr =xxxxxxx server_port = 7000 tls_enable = true [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000` 版本：frp_0.38.0_linux_amd64

gitea-mirror commented

2026-05-05 13:00:22 -06:00

Author

Owner

@ywhao88 commented on GitHub (Aug 28, 2022):

具体看这篇博客https://blog.phpgao.com/frp_tcp_reset.html
你的网络可能把frp屏蔽了，换0.25.0以上的frp，开通tls传输

@ywhao88 commented on GitHub (Aug 28, 2022): 具体看这篇博客https://blog.phpgao.com/frp_tcp_reset.html 你的网络可能把frp屏蔽了，换0.25.0以上的frp，开通tls传输

gitea-mirror commented

2026-05-05 13:00:23 -06:00

Author

Owner

@programmer-zheng commented on GitHub (Nov 25, 2024):

亲测：frpc.ini 加上 tls_enable = true 即可 `[common] server_addr =xxxxxxx server_port = 7000 tls_enable = true

[ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000` 版本：frp_0.38.0_linux_amd64

版本：0.47.0
感谢，有用，解决问题了

@programmer-zheng commented on GitHub (Nov 25, 2024): > 亲测：frpc.ini 加上 tls_enable = true 即可 `[common] server_addr =xxxxxxx server_port = 7000 tls_enable = true > > [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000` 版本：frp_0.38.0_linux_amd64 版本：0.47.0 感谢，有用，解决问题了