mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #4905] [Bug] frpc lost connection and reconnect to frps from time to time without any error log #3869
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#3869
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Logs
Steps to reproduce
No response
Affected area
@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?
@link89 commented on GitHub (Jul 31, 2025):
Isn't 0.63.0 the latest version?
@fatedier commented on GitHub (Jul 31, 2025):
You haven't used the 0.63.0 version.
@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.
@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.