¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Xephem
  2. Messages
Single Messages Topics Expanded Polls

Re: SOLVED: Error "https get: sohowww.nascom.nasa.gov: ssl send error code: 1" on OS X El Capitan

 

Hi trane,

Thank you for sharing that! I run an older Mac (G4 iBook 12") and I tried building xephem on my OS X 10.5.8 installation. It failed for some reason (can't recall the error - will have to try again!), but I have compiled and run it on Arch Linux before (including the SOHO patch). I recently upgraded from XCode 3.0 to 3.1 - I am wondering if I should try again.

I too purchased the commercial version and I love it! I do miss it as the little Mac is now my main computer (the IBM ThinkPad R40 running Arch doesn't see too much action these days). I am a lover of old hardware. :)

Anyway thanks again! You've inspired me to give it another shot.

Thanks!

Rick in Canada (eh!)

On 2-Aug-17, at 12:25 AM, Trane Francks trane@... [xephem] wrote:

?

Hi, everybody.

FIRST: Let me arrive late to the party and say thank you to Elwood for so many great years of XEphem. I started with XEphem back in 2003 on Linux and then migrated seamlessly over to OS X in 2007. I was a happy commercial user and have never regretted the purchase. Thanks, Elwood!

~~~~~~~

Mac OS X 10.11.6 El Capitan user here. I've just finished compiling 3.7.7 with the below-mentioned patch and I wanted to share my solution for the below error seen when attempting to download the the latest SOHO files:

https get: sohowww.nascom.nasa.gov: ssl send error code: 1

The patch was successfully applied, since this error is different than with the unpatched build. The OpenSSL version originally shipped with El Capitan is: OpenSSL 0.9.8zh 3 Dec 2015.

Apple stopped shipping the header files, so I ended up downloading the full source for the original version and compiling against that. Unfortunately, that results in the error seen above. I'm assuming that their side was refusing the connection because the old OpenSSL version couldn't do better than TLS 1.0.

SOLUTION: Download the latest (currently OpenSSL 1.1.0f? 25 May 2017), compile, install and try again. Given that Apple is deprecating OpenSSL in favour of their own stuff, I chose to set the installation prefix to '/usr' and overwrite the system installation. You pays your money and you takes your chances.

Cheers, everybody.

trane

//
// Trane Francks trane@... Tokyo, Japan
// Practice random kindness and senseless acts of beauty.

On 11/8/16 12:17 AM, ecdowney@... [xephem] wrote:
?

Check the "User contrib" area, there is a patch for using openssl to access SOHO.


Elwood
Join [email protected] to automatically receive all group messages.