[GH-ISSUE #2571] frp 内网穿透btc节点超时

Originally created by @LongTaijun on GitHub (Sep 9, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2571 ### Bug Description 我的frp代理内网btc的rpc接口访问不了，但是内网ip请求没问题的，访问皆是502超时，看了frp的日志，每次都是10秒就自己关闭了貌似，请求访问10s过后返回的是join connections closed，因为请求的btc的getinfo信息，所以返回时间会很长，感觉是frp自己关闭了连接，配置了user_conn_timeout = 300也不好使，看这个参数默认也是10s，请问这个10s超时问题怎么解决？ ### frpc Version 0.37.1 ### frps Version 0.37.1 ### System Architecture linux amd64 ### Configurations frps： [common] bind_port = 7000 dashboard_port = 7500 token = btcandeth dashboard_user = xxx dashboard_pwd = xxx vhost_http_port = 10080 vhost_https_port = 10443 vhost_http_timeout = 900 host_http_timeout = 300 authentication_timeout = 900 user_conn_timeout = 300 heartbeat_timeout = 300 tcp_mux = true log_level = trace frpc： [common] server_addr = x.x.x.x server_port = 7000 token = xxx health_check_interval_s = 300 tcp_mux = true heartbeat_interval = 300 heartbeat_timeout = 900 log_level = trace user_conn_timeout = 300 [btc] type = tcp local_ip = 127.0.0.1 local_port = 8666 remote_port = 18666 custom_domains = x.x.x [eth] type = tcp local_ip = 127.0.0.1 local_port = 8545 remote_port = 18545 custom_domains = x.x.x ### Logs frps： 2021/09/09 10:18:35 [I] [proxy.go:179] [2563afb14892f72b] [btc] get a user connection [x.x.x.x:26818] 2021/09/09 10:18:35 [D] [control.go:248] [2563afb14892f72b] get work connection from pool 2021/09/09 10:18:35 [D] [proxy.go:104] [2563afb14892f72b] [btc] get a new work connection: [x.x.x.x:40900] 2021/09/09 10:18:35 [T] [proxy.go:279] [2563afb14892f72b] [btc] handler user tcp connection, use_encryption: false, use_compression: false 2021/09/09 10:18:35 [D] [proxy.go:290] [2563afb14892f72b] [btc] join connections, workConn(l[192.168.1.3:7000] r[110.191.218.29:40900]) userConn(l[192.168.1.3:18666] r[x.x.x.x:26818]) 2021/09/09 10:18:35 [D] [control.go:219] [2563afb14892f72b] new work connection registered 2021/09/09 10:18:45 [D] [proxy.go:300] [2563afb14892f72b] [btc] join connections closed frpc： 2021/09/09 10:18:35 [D] [proxy_wrapper.go:231] [2563afb14892f72b] [btc] start a new work connection, localAddr: 192.168.31.22:55722 remoteAddr: x.x.x.x:7000 2021/09/09 10:18:35 [T] [proxy.go:739] [2563afb14892f72b] [btc] handle tcp work connection, use_encryption: false, use_compression: false 2021/09/09 10:18:35 [D] [proxy.go:801] [2563afb14892f72b] [btc] join connections, localConn(l[127.0.0.1:53982] r[127.0.0.1:8666]) workConn(l[192.168.31.22:55722] r[x.x.x.x:7000]) 2021/09/09 10:18:45 [D] [proxy.go:809] [2563afb14892f72b] [btc] join connections closed ### Steps to reproduce _No response_ ### Affected area - [X] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [X] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror commented

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

Owner

Originally created by @LongTaijun on GitHub (Sep 9, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2571

Bug Description

我的frp代理内网btc的rpc接口访问不了，但是内网ip请求没问题的，访问皆是502超时，看了frp的日志，每次都是10秒就自己关闭了貌似，请求访问10s过后返回的是join connections closed，因为请求的btc的getinfo信息，所以返回时间会很长，感觉是frp自己关闭了连接，配置了user_conn_timeout = 300也不好使，看这个参数默认也是10s，请问这个10s超时问题怎么解决？

frpc Version

0.37.1

frps Version

System Architecture

linux amd64

Configurations

frps：
[common]
bind_port = 7000
dashboard_port = 7500
token = btcandeth
dashboard_user = xxx
dashboard_pwd = xxx
vhost_http_port = 10080
vhost_https_port = 10443
vhost_http_timeout = 900
host_http_timeout = 300
authentication_timeout = 900
user_conn_timeout = 300
heartbeat_timeout = 300
tcp_mux = true
log_level = trace

frpc：
[common]
server_addr = x.x.x.x
server_port = 7000
token = xxx
health_check_interval_s = 300
tcp_mux = true
heartbeat_interval = 300
heartbeat_timeout = 900
log_level = trace
user_conn_timeout = 300

[btc]
type = tcp
local_ip = 127.0.0.1
local_port = 8666
remote_port = 18666
custom_domains = x.x.x

[eth]
type = tcp
local_ip = 127.0.0.1
local_port = 8545
remote_port = 18545
custom_domains = x.x.x

Logs

frps：
2021/09/09 10:18:35 [I] [proxy.go:179] [2563afb14892f72b] [btc] get a user connection [x.x.x.x:26818]
2021/09/09 10:18:35 [D] [control.go:248] [2563afb14892f72b] get work connection from pool
2021/09/09 10:18:35 [D] [proxy.go:104] [2563afb14892f72b] [btc] get a new work connection: [x.x.x.x:40900]
2021/09/09 10:18:35 [T] [proxy.go:279] [2563afb14892f72b] [btc] handler user tcp connection, use_encryption: false, use_compression: false
2021/09/09 10:18:35 [D] [proxy.go:290] [2563afb14892f72b] [btc] join connections, workConn(l[192.168.1.3:7000] r[110.191.218.29:40900]) userConn(l[192.168.1.3:18666] r[x.x.x.x:26818])
2021/09/09 10:18:35 [D] [control.go:219] [2563afb14892f72b] new work connection registered
2021/09/09 10:18:45 [D] [proxy.go:300] [2563afb14892f72b] [btc] join connections closed

frpc：

2021/09/09 10:18:35 [D] [proxy_wrapper.go:231] [2563afb14892f72b] [btc] start a new work connection, localAddr: 192.168.31.22:55722 remoteAddr: x.x.x.x:7000
2021/09/09 10:18:35 [T] [proxy.go:739] [2563afb14892f72b] [btc] handle tcp work connection, use_encryption: false, use_compression: false
2021/09/09 10:18:35 [D] [proxy.go:801] [2563afb14892f72b] [btc] join connections, localConn(l[127.0.0.1:53982] r[127.0.0.1:8666]) workConn(l[192.168.31.22:55722] r[x.x.x.x:7000])
2021/09/09 10:18:45 [D] [proxy.go:809] [2563afb14892f72b] [btc] join connections closed

Steps to reproduce

No response

Affected area

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

gitea-mirror

closed this issue
added the
lifecycle/stale
label

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

Author

@fatedier commented on GitHub (Sep 9, 2021):

TCP 的 proxy 在 frp 这一层没有超时，如果断开了连接，建议排查一下你自己的服务里有没有相关的配置。

@fatedier commented on GitHub (Sep 9, 2021): TCP 的 proxy 在 frp 这一层没有超时，如果断开了连接，建议排查一下你自己的服务里有没有相关的配置。

@LongTaijun commented on GitHub (Sep 9, 2021):

TCP的代理在frp这一层没有，如果已经连接了，建议排一下你自己的服务里有没有相关的配置。

感觉有点儿解释不通，因为我内网访问我的服务rpc接口都能正常返回，但是frp出去访问每次都是十秒返回502，要是服务有问题，内网直接访问也应该超时的。

@LongTaijun commented on GitHub (Sep 9, 2021): > TCP的代理在frp这一层没有，如果已经连接了，建议排一下你自己的服务里有没有相关的配置。感觉有点儿解释不通，因为我内网访问我的服务rpc接口都能正常返回，但是frp出去访问每次都是十秒返回502，要是服务有问题，内网直接访问也应该超时的。

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

@github-actions[bot] commented on GitHub (Oct 10, 2021):

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 10, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

Rows
Columns

[GH-ISSUE #2571] frp 内网穿透btc节点超时 #2045