If you’ve been around Rails long enough, you’ve probably battled your fair share of SSL demons. But this one? This one had personality . It was a Seahorse::Client::NetworkingError that failed only on macOS — yet worked perfectly inside Docker. The kind of “it works on my container” bug that makes you question every life choice leading up to this point. So here’s the story of how we chased down a ghostly SSL error, only to discover that the real culprit was… OpenSSL itself. ⚠️ The Error Seahorse::Client::NetworkingError SSL_connect returned=1 errno=0 peeraddr=[...] state=error: certificate verify failed (unable to get certificate CRL) This popped up whenever our Rails app tried connecting to AWS S3 using the aws-sdk-ruby gem. 🔍 The Contradiction That Made No Sense From the get-go, the bug refused to play by any rules of logic. ❌ It failed locally but ✅ Worked flawlessly in Docker That told us one thing: the problem wasn’t our code. It was the environment. macOS and Dock...
If you’ve been around Rails long enough, you’ve probably battled your fair share of SSL demons. But this one? This one had personality . It was a Seahorse::Client::NetworkingError that failed only on macOS — yet worked perfectly inside Docker. The kind of “it works on my container” bug that makes you question every life choice leading up to this point. So here’s the story of how we chased down a ghostly SSL error, only to discover that the real culprit was… OpenSSL itself. ⚠️ The Error Seahorse::Client::NetworkingError SSL_connect returned=1 errno=0 peeraddr=[...] state=error: certificate verify failed (unable to get certificate CRL) This popped up whenever our Rails app tried connecting to AWS S3 using the aws-sdk-ruby gem. 🔍 The Contradiction That Made No Sense From the get-go, the bug refused to play by any rules of logic. ❌ It failed locally but ✅ Worked flawlessly in Docker That told us one thing: the problem wasn’t our code. It was the environment. macOS and Dock...