Closed pierre-pretorius closed 6 months ago
@pierre-pretorius I looked into it, but I couldn't figure out under what circumstances this issue would occur. It's quite strange. Are you using the binary files downloaded from GitHub or did you compile it yourself?
In addition, starting from version 0.50.0, TLS will be enabled by default. The traffic between frpc and frps will be encrypted, so you no longer need to use use_encryption = true
.
@pierre-pretorius I looked into it, but I couldn't figure out under what circumstances this issue would occur. It's quite strange. Are you using the binary files downloaded from GitHub or did you compile it yourself?
I'm using the binary from Github
@pierre-pretorius I have discovered a race condition issue, but I am not sure if it is related to your problem. I will fix this issue and release a minor version.
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Bug Description
We did get the
slice bounds out of range
error in thecipher
code in previous versions, but we upgraded to the latest 0.51.0 to ensure the bug is present in the latest code. It looks like the stack trace in the log below is too short to determine the root cause?frpc Version
Various versions from 0.34.0 and upwards
frps Version
0.51.0
System Architecture
linux/amd64
Configurations
Server
Client
Logs
Steps to reproduce
We only see this error on high traffic servers, so it's not easy to reproduce. It happens more or less every day.
Affected area