http error ssl handshake failed

[lassyVkatsu]

ive been trying to install rock box on a first gen nano but when i try to install it i keep getting a Download error

Download error: received HTTP error SSL handshake failed.

i tried to attach a log file but is 367 kb and the max is 256kb here soo imma post one with some lines deleted to get it under the size limit

[lassyVkatsu]

my os is ubuntu 20.04.1 LTS
i tried messing with proxy settings and different networks but rockbox refuses to connect
im running it with admin (sudo) too
all other app in my laptop work perfectly all connects with no issues but rockbox utility is the only app that refuses to connect

[Punt]

I'm having a similar issue on Linux Mint 21 (based on Ubuntu 22.04), trying to install Rockbox on an iPod 6G. The Rockbox Utility can't communicate with site, "Network error: SSL handshake failed."

I must point out that this looks to be specific to the Linux version.  I've just tried the 1.5.1 installer on Windows and it works. 

[eugenkss]

I have the same issue. I am on Linux Mint 22.

Version 1.4.1 of the Rockbox Utility works without this problem though.

[eugenkss]

Today, I built Rockbox Utility from source, and with the resulting executable there is no such SSL handshake error anymore 

[dotbrush]

same issue with ubuntu 22.04. same resolution -- using previous version of rockbox utility.

then had to apt install libcrypt++-dev to run the executable.

[phinken]

I have the same problem on Pop_os! 22.04 - surely this is a bug that can be fixed relatively easily if it works on Windows?
I don't have access to any computers with windows, so I have to make this work in Linux somehow.

Version 1.4.1 of the Rockbox Utility works without this problem though.

I just tried 1.4.1, had to install a few library packages that were missing to run the executable, but still the same problem. I even got a popup as soon as i ran the executable, saying network connection failed. I executed as root, btw.

I guess my next thing to try is building from source, whch is something I have to learn first...

[phinken]

The connection worked after building from source! But only when I didn't run as root, for some reason.

My problem now is that there is no partition table download for my iPod version: https://forums.rockbox.org/index.php/topic,54429.msg251483.html#msg251483

[bluebrother]

I have the same problem on Pop_os! 22.04 - surely this is a bug that can be fixed relatively easily if it works on Windows?

This is not a bug in Rockbox Utility. It works totally fine on both a current Debian stable and Fedora for me. My guess is that Qt (which does the SSL stuff for us) dynamically loads some library that isn't present on your machine, but since it dynamically loads it there's no direct way to see that. Or maybe it's its handling of the cert store (the OP log has Got SSL error ("The peer did not present any certificate") in it.) The problem is that this is not easy to figure. So either it's a problem with your setup -- or some library missing in the AppImage that causes this. If you have any clue what's causing that please let me know (running it with strace might help)

I don't have access to any computers with windows, so I have to make this work in Linux somehow.

You can always compile yourself. It's not a Rockbox Utility bug, so building yourself will work. And the older 1.4.1 did work since that wasn't an AppImage but a statically linked binary instead. Which caused tons of other problems -- deploying distro-independent binaries on Linux is unfortunately rather messy. But if you're familiar with that: help is welcome. I'd personally go as far as not distributing binaries for Linux anymore, since they tend to cause all kinds of issues. And Linux users usually can compile things themselves (well, at least the ones that want to replace firmware files.)

Edit:
Can you please check if you have a libssl.so.1.1 somewhere in your system lib search path?

[phinken]

Thank you, that explains it a bit more 

You can always compile yourself. It's not a Rockbox Utility bug, so building yourself will work. And the older 1.4.1 did work since that wasn't an AppImage but a statically linked binary instead.

...although I did try 1.4.1 and had the same problem. And I do get the problem with 1.5.1 built from source if I try to run as root. I regret that I don't understand my system well enough to have any suspicion of what might have gone wrong... I'm just glad I got it to work in the end (1.5.1 built from source, ran without root permission). My next issue is a problem with the iPod itself and the installation process, which is a topic for another thread.

Edit:
Can you please check if you have a libssl.so.1.1 somewhere in your system lib search path?

I'm away for work at the moment, but bill check this out when I get back. Thanks for the help!

[phinken]

Can you please check if you have a libssl.so.1.1 somewhere in your system lib search path?

No, I don't have that.

[bluebrother]

No, I don't have that.

Ok, that seems to be a pointer. Checking Ubuntu 22.04 package lists it appears they aren't shipping OpenSSL 1.1.1 anymore and only have OpenSSL 3. Both Debian and (a current!) Fedora still ship it. Qt seems to dynamically load libssl.so.1.1, but since OpenSSL 3 bumped the soname to libssl.so.3 this obviously won't match. And since it is loaded during runtime building the AppImage cannot know about it.

Can you run it with strace and see if it's trying to open libssl.so.1.1 on your machine? Also, do you have /usr/lib/x86_64-linux-gnu/libssl.so.3 (you should, it's part of the libssl3 package on Ubuntu)?

And why does Ubuntu always break things? OpenSSL 1.1.1 is still maintained.

Update: Turns out this is indeed an issue with a dynamically loaded libssl.so. On Ubuntu 22.04 only openssl 3 is shipped. Qt tries to load the libssl.so.3 on that, which (at least as far as I can see) works but using it doesn't -- after all, it's a major version update so this isn't completely unexpected. Compiling openssl 1.1.1 manually on such a box does make things work. So the bottom line is that we'd need a reasonable way to put libssl.so.1.1 into the AppImage, but the appimage tools aren't able to automatically do that since RockboxUtility isn't linked against it (and the Qt libs aren't either.)

[pssss]

Thanks for the help @bluebrother

I was able to resolve tthe SSL failure issue by manually installing openssl as described here: https://stackoverflow.com/a/73604364/667913

This is on Ubuntu Ubuntu 22.04.1 LTS