[GH-ISSUE #3613] http: TLS handshake error from xxxx:xxxx: EOF #2881

New issue

Closed

opened 2026-05-05 13:51:43 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 13:51:43 -06:00

Owner

Originally created by @steveoon on GitHub (Sep 14, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3613

Bug Description

非大陆区在亚马逊部署的frps，然后客户端macOS部署了frpc，链接成功但是运行一段时间后就发现报错：
http: TLS handshake error from xxxx:xxxx: EOF

启用了https2http插件，把本地http服务转为https，配置参考下面。
不知道什么原因，求大神帮助。

frpc Version

frp_0.51.3_darwin_arm64

frps Version

frp_0.51.3_linux_amd64

System Architecture

GNU/Linux 5.19.0-1025-aws x86_64, macOS 13.5.2 (22G91)

Configurations

frps

[common]
bind_port = xxxx
token = xxx
vhost_https_port = 443
max_pool_count = 5
subdomain_host = xxx.xxx

dashboard_port = xxxx
dashboard_user = xxx
dashboard_pwd = xxx

dashboard_tls_mode = true
dashboard_tls_cert_file = /etc/letsencrypt/live/xxx/fullchain.pem
dashboard_tls_key_file = /etc/letsencrypt/live/xxx/privkey.pem

# TLS 配置
tls_only = true
tls_cert_file = /etc/letsencrypt/live/xxx/fullchain.pem
tls_key_file = /etc/letsencrypt/live/xxx/privkey.pem

frpc

[common]
server_addr = x.x.x.x
server_port = xxxx
token = xx
pool_count = 5

admin_addr = 127.0.0.1
admin_port = 7430
admin_user = xx 
admin_pwd = xx

tcp_mux_keepalive_interval = 60
heartbeat_interval = -1

[test_htts2http]
type = https
custom_domains = xxxx.xxx

plugin = https2http
plugin_local_addr = 127.0.0.1:8000

# HTTPS 证书相关的配置
plugin_crt_path = /Users/xxx/Documents/cert/fullchain.pem
plugin_key_path = /Users/xxx/Documents/cert/privkey.pem
plugin_host_header_rewrite = 127.0.0.1
plugin_header_X-From-Where = frp

subdomain = api

Logs

frpc

2023/09/14 14:05:18 [I] [control.go:252] [04136abe6b8ec005] control writer is closing
2023/09/14 14:05:18 [I] [visitor_manager.go:77] [04136abe6b8ec005] gracefully shutdown visitor manager
2023/09/14 14:05:18 [I] [service.go:214] [04136abe6b8ec005] try to reconnect to server...
2023/09/14 14:05:21 [I] [service.go:301] [04136abe6b8ec005] login to server success, get run id [04136abe6b8ec005]
2023/09/14 14:05:21 [I] [proxy_manager.go:150] [04136abe6b8ec005] proxy added: [test_htts2http]
2023/09/14 14:05:21 [I] [control.go:172] [04136abe6b8ec005] [test_htts2http] start proxy success
2023/09/14 15:42:44 http: TLS handshake error from xxxx:xxxx: EOF
2023/09/14 15:42:44 http: TLS handshake error from  xxxx:xxxx: EOF
2023/09/14 15:42:45 http: TLS handshake error from  xxxx:xxxx: EOF
2023/09/14 15:42:45 http: TLS handshake error from  xxxx:xxxx: EOF
2023/09/14 15:42:45 http: TLS handshake error from  xxxx:xxxx: EOF

frps

Sep 14 14:05:18 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:18 [I] [control.go:332] [04136abe6b8ec005] control writer is closing
Sep 14 14:05:18 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:18 [I] [proxy.go:110] [04136abe6b8ec005] [test_htts2http] proxy clo>
Sep 14 14:05:18 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:18 [I] [control.go:421] [04136abe6b8ec005] client exit success
Sep 14 14:05:18 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:18 [W] [proxy.go:196] [04136abe6b8ec005] [test_htts2http] listener >
Sep 14 14:05:18 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:18 [W] [proxy.go:196] [04136abe6b8ec005] [test_htts2http] listener >
Sep 14 14:05:19 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:19 [I] [service.go:539] [04136abe6b8ec005] client login info: ip [5>
Sep 14 14:05:21 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:21 [I] [https.go:67] [04136abe6b8ec005] [test_htts2http] https prox>
Sep 14 14:05:21 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:21 [I] [https.go:79] [04136abe6b8ec005] [test_htts2http] https prox>
Sep 14 14:05:21 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:21 [I] [control.go:497] [04136abe6b8ec005] new proxy [test_htts2htt>
Sep 14 15:42:43 ip-x-x-x-x frps[40071]: 2023/09/14 07:42:43 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use>
Sep 14 15:42:44 ip-x-x-x-x frps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use>
Sep 14 15:42:44 ip-x-x-x-xfrps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use>
Sep 14 15:42:44 ip-1x-x-x-x frps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use>
Sep 14 15:42:44 ip-x-x-x-xfrps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use>
Sep 14 15:42:45 ip-v frps[40071]: 2023/09/14 07:42:45 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use>

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @steveoon on GitHub (Sep 14, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3613 ### Bug Description 非大陆区在亚马逊部署的frps，然后客户端macOS部署了frpc，链接成功但是运行一段时间后就发现报错： `http: TLS handshake error from xxxx:xxxx: EOF` 启用了https2http插件，把本地http服务转为https，配置参考下面。不知道什么原因，求大神帮助。 ### frpc Version frp_0.51.3_darwin_arm64 ### frps Version frp_0.51.3_linux_amd64 ### System Architecture GNU/Linux 5.19.0-1025-aws x86_64, macOS 13.5.2 (22G91) ### Configurations frps ``` [common] bind_port = xxxx token = xxx vhost_https_port = 443 max_pool_count = 5 subdomain_host = xxx.xxx dashboard_port = xxxx dashboard_user = xxx dashboard_pwd = xxx dashboard_tls_mode = true dashboard_tls_cert_file = /etc/letsencrypt/live/xxx/fullchain.pem dashboard_tls_key_file = /etc/letsencrypt/live/xxx/privkey.pem # TLS 配置 tls_only = true tls_cert_file = /etc/letsencrypt/live/xxx/fullchain.pem tls_key_file = /etc/letsencrypt/live/xxx/privkey.pem ``` frpc ``` [common] server_addr = x.x.x.x server_port = xxxx token = xx pool_count = 5 admin_addr = 127.0.0.1 admin_port = 7430 admin_user = xx admin_pwd = xx tcp_mux_keepalive_interval = 60 heartbeat_interval = -1 [test_htts2http] type = https custom_domains = xxxx.xxx plugin = https2http plugin_local_addr = 127.0.0.1:8000 # HTTPS 证书相关的配置 plugin_crt_path = /Users/xxx/Documents/cert/fullchain.pem plugin_key_path = /Users/xxx/Documents/cert/privkey.pem plugin_host_header_rewrite = 127.0.0.1 plugin_header_X-From-Where = frp subdomain = api ``` ### Logs frpc ``` 2023/09/14 14:05:18 [I] [control.go:252] [04136abe6b8ec005] control writer is closing 2023/09/14 14:05:18 [I] [visitor_manager.go:77] [04136abe6b8ec005] gracefully shutdown visitor manager 2023/09/14 14:05:18 [I] [service.go:214] [04136abe6b8ec005] try to reconnect to server... 2023/09/14 14:05:21 [I] [service.go:301] [04136abe6b8ec005] login to server success, get run id [04136abe6b8ec005] 2023/09/14 14:05:21 [I] [proxy_manager.go:150] [04136abe6b8ec005] proxy added: [test_htts2http] 2023/09/14 14:05:21 [I] [control.go:172] [04136abe6b8ec005] [test_htts2http] start proxy success 2023/09/14 15:42:44 http: TLS handshake error from xxxx:xxxx: EOF 2023/09/14 15:42:44 http: TLS handshake error from xxxx:xxxx: EOF 2023/09/14 15:42:45 http: TLS handshake error from xxxx:xxxx: EOF 2023/09/14 15:42:45 http: TLS handshake error from xxxx:xxxx: EOF 2023/09/14 15:42:45 http: TLS handshake error from xxxx:xxxx: EOF ``` frps ``` Sep 14 14:05:18 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:18 [I] [control.go:332] [04136abe6b8ec005] control writer is closing Sep 14 14:05:18 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:18 [I] [proxy.go:110] [04136abe6b8ec005] [test_htts2http] proxy clo> Sep 14 14:05:18 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:18 [I] [control.go:421] [04136abe6b8ec005] client exit success Sep 14 14:05:18 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:18 [W] [proxy.go:196] [04136abe6b8ec005] [test_htts2http] listener > Sep 14 14:05:18 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:18 [W] [proxy.go:196] [04136abe6b8ec005] [test_htts2http] listener > Sep 14 14:05:19 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:19 [I] [service.go:539] [04136abe6b8ec005] client login info: ip [5> Sep 14 14:05:21 ip-x-x-x-xfrps[40071]: 2023/09/14 06:05:21 [I] [https.go:67] [04136abe6b8ec005] [test_htts2http] https prox> Sep 14 14:05:21 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:21 [I] [https.go:79] [04136abe6b8ec005] [test_htts2http] https prox> Sep 14 14:05:21 ip-x-x-x-x frps[40071]: 2023/09/14 06:05:21 [I] [control.go:497] [04136abe6b8ec005] new proxy [test_htts2htt> Sep 14 15:42:43 ip-x-x-x-x frps[40071]: 2023/09/14 07:42:43 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use> Sep 14 15:42:44 ip-x-x-x-x frps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use> Sep 14 15:42:44 ip-x-x-x-xfrps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use> Sep 14 15:42:44 ip-1x-x-x-x frps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use> Sep 14 15:42:44 ip-x-x-x-xfrps[40071]: 2023/09/14 07:42:44 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use> Sep 14 15:42:45 ip-v frps[40071]: 2023/09/14 07:42:45 [I] [proxy.go:199] [04136abe6b8ec005] [test_htts2http] get a use> ``` ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:51:43 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:51:46 -06:00

Author

Owner

@caiwenmin commented on GitHub (Sep 25, 2023):

你好像也是frpc的时区错误了，你看两个日志的时间，相差好几个小时，我也遇到了，frpc的日志时间与机器时间不一致

@caiwenmin commented on GitHub (Sep 25, 2023): 你好像也是frpc的时区错误了，你看两个日志的时间，相差好几个小时，我也遇到了，frpc的日志时间与机器时间不一致

gitea-mirror commented

2026-05-05 13:51:47 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 26, 2023):

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

@github-actions[bot] commented on GitHub (Oct 26, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.