-
Notifications
You must be signed in to change notification settings - Fork 2.9k
"SSL peer certificate or SSH remote key was not OK" error on FreeBSD #16357
Copy link
Copy link
Closed
Copy link
Labels
A-networkingArea: networking issues, curl, etc.Area: networking issues, curl, etc.C-bugCategory: bugCategory: bugO-freebsdOS: FreeBSDOS: FreeBSDregression-from-stable-to-betaRegression in beta that previously worked in stable.Regression in beta that previously worked in stable.regression-from-stable-to-stableRegression in stable that worked in a previous stable release.Regression in stable that worked in a previous stable release.
Metadata
Metadata
Assignees
Labels
A-networkingArea: networking issues, curl, etc.Area: networking issues, curl, etc.C-bugCategory: bugCategory: bugO-freebsdOS: FreeBSDOS: FreeBSDregression-from-stable-to-betaRegression in beta that previously worked in stable.Regression in beta that previously worked in stable.regression-from-stable-to-stableRegression in stable that worked in a previous stable release.Regression in stable that worked in a previous stable release.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Nominated
View all comments
Problem
All of my CI jobs that use nightly Rust on FreeBSD began to fail on about 4-December with this error:
The CI environment has not changed, I don't see this problem on stable Rust, and I don't see this problem on Linux. Nor have I yet been able to reproduce the problem on a local FreeBSD VM.
Links to some failed builds:
https://cirrus-ci.com/task/5129181652058112
https://cirrus-ci.com/task/6459889154785280
https://cirrus-ci.com/task/5444677467373568
https://cirrus-ci.com/task/6421169420632064
Steps
Possible Solution(s)
No response
Notes
No response
Version