SSL EOF occurred in violation of protocol when syncing dist folder to R2 bucket #3559
Description
Hey all! As a part of #3461, the /home/dist/ folder started to be synced into a R2 bucket. The behavior was added in #3505.
It was working fine for nightly builds up until it came time to promote v18.18.1, where it threw a bunch of SSL errors reported here #3508 (comment).
The error is due to EOF occurred in violation of protocol. I am not sure what exactly the issue is, however I do have some theories:
- A bug/other issue with the openssl version installed on the DO server (doesn't really explain why the nightly builds were being successfully synced however)
- Different users on the DO server have different CA certs installed. The automated user that runs the uploads of the nightly builds has the correct CA certs installed while other users may not, leading to SSL errors for only certain users.
Unfortunately since the sync script was failing it had to be disabled, so the R2 bucket is becoming more and more stale. This issue also blocks #3461 entirely since we're no longer getting new builds added to the bucket.
Ideally we would be able to figure out what is causing the issue, fix it, and then re-enable the sync script for new releases in addition to syncing the downloads that were added over the course of syncing being disabled