[GH-ISSUE #4905] [Bug] frpc lost connection and reconnect to frps from time to time without any error log #3869

Closed
opened 2026-05-05 14:28:21 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @link89 on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4905

Bug Description

I am using frp's tcp proxy to publish a intranet web app to internet, nginx is used for https support.

But I find in nginx log that there are 502 errors from time to time. frps log shows nothing wrong, but fprc log shows it reconnect to server from time to time without any error message. Whenever reconnect happens, the nginx will start to raise 502 errors.

I have no idea why it happens.

frpc Version

0.63.0

frps Version

0.63.0

System Architecture

linux/amd64

Configurations

#frps
bindAddr = "0.0.0.0"
bindPort = 7000
#frpc
serverAddr = 
serverPort = 7000


[[proxies]]
name = "scow"
type = "tcp"

localIP = 
localPort = 8080
remotePort = 9090

Logs

2025-07-31 06:58:33.399 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 06:58:34.835 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 06:58:34.835 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 06:58:34.904 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 06:59:13.665 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 06:59:14.059 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 06:59:14.059 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 06:59:14.126 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 07:07:55.313 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 07:07:59.928 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 07:07:59.928 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 07:08:00.148 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 07:09:05.636 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 07:09:06.032 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 07:09:06.033 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 07:09:06.101 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 07:29:24.254 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 07:29:24.655 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 07:29:24.656 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 07:29:24.725 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 07:35:35.291 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 07:35:35.662 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 07:35:35.662 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 07:35:35.725 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 07:44:16.856 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 07:44:17.261 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 07:44:17.262 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 07:44:17.332 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 08:06:30.360 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 08:06:30.767 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 08:06:30.768 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 08:06:30.836 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 08:12:41.468 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 08:12:41.846 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 08:12:41.847 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 08:12:41.909 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success
2025-07-31 08:29:23.896 [I] [client/service.go:314] [3279d36990209270] try to connect to server...
2025-07-31 08:29:24.292 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270]
2025-07-31 08:29:24.293 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow]
2025-07-31 08:29:24.365 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success    

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
Originally created by @link89 on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4905 ### Bug Description I am using frp's tcp proxy to publish a intranet web app to internet, nginx is used for https support. But I find in nginx log that there are 502 errors from time to time. frps log shows nothing wrong, but fprc log shows it reconnect to server from time to time without any error message. Whenever reconnect happens, the nginx will start to raise 502 errors. I have no idea why it happens. ### frpc Version 0.63.0 ### frps Version 0.63.0 ### System Architecture linux/amd64 ### Configurations ``` #frps bindAddr = "0.0.0.0" bindPort = 7000 ``` ``` #frpc serverAddr = serverPort = 7000 [[proxies]] name = "scow" type = "tcp" localIP = localPort = 8080 remotePort = 9090 ``` ### Logs ``` 2025-07-31 06:58:33.399 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 06:58:34.835 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 06:58:34.835 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 06:58:34.904 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 06:59:13.665 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 06:59:14.059 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 06:59:14.059 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 06:59:14.126 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 07:07:55.313 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 07:07:59.928 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 07:07:59.928 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 07:08:00.148 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 07:09:05.636 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 07:09:06.032 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 07:09:06.033 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 07:09:06.101 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 07:29:24.254 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 07:29:24.655 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 07:29:24.656 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 07:29:24.725 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 07:35:35.291 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 07:35:35.662 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 07:35:35.662 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 07:35:35.725 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 07:44:16.856 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 07:44:17.261 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 07:44:17.262 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 07:44:17.332 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 08:06:30.360 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 08:06:30.767 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 08:06:30.768 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 08:06:30.836 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 08:12:41.468 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 08:12:41.846 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 08:12:41.847 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 08:12:41.909 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success 2025-07-31 08:29:23.896 [I] [client/service.go:314] [3279d36990209270] try to connect to server... 2025-07-31 08:29:24.292 [I] [client/service.go:306] [3279d36990209270] login to server success, get run id [3279d36990209270] 2025-07-31 08:29:24.293 [I] [proxy/proxy_manager.go:177] [3279d36990209270] proxy added: [scow] 2025-07-31 08:29:24.365 [I] [client/control.go:172] [3279d36990209270] [scow] start proxy success ```` ### 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 2026-05-05 14:28:21 -06:00
Author
Owner

@fatedier commented on GitHub (Jul 31, 2025):

From your logs, it looks like your client version is not 0.63.0. Could you try updating it first?

<!-- gh-comment-id:3139474252 --> @fatedier commented on GitHub (Jul 31, 2025): From your logs, it looks like your client version is not 0.63.0. Could you try updating it first?
Author
Owner

@link89 commented on GitHub (Jul 31, 2025):

Isn't 0.63.0 the latest version?

<!-- gh-comment-id:3139860816 --> @link89 commented on GitHub (Jul 31, 2025): Isn't 0.63.0 the latest version?
Author
Owner

@fatedier commented on GitHub (Jul 31, 2025):

You haven't used the 0.63.0 version.

<!-- gh-comment-id:3139953567 --> @fatedier commented on GitHub (Jul 31, 2025): You haven't used the 0.63.0 version.
Author
Owner

@link89 commented on GitHub (Jul 31, 2025):

I am using this https://github.com/fatedier/frp/releases/download/v0.63.0/frp_0.63.0_linux_amd64.tar.gz in both server and client.

<!-- gh-comment-id:3140708599 --> @link89 commented on GitHub (Jul 31, 2025): I am using this https://github.com/fatedier/frp/releases/download/v0.63.0/frp_0.63.0_linux_amd64.tar.gz in both server and client.
Author
Owner

@github-actions[bot] commented on GitHub (Aug 15, 2025):

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

<!-- gh-comment-id:3190293856 --> @github-actions[bot] commented on GitHub (Aug 15, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
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#3869
No description provided.