"unsafe legacy renegotiation disabled" error when using curl on shortened links #1464
-
How Shlink is set-up
SummaryGreetings! Phenomenal tool. Thanks so much for all the hard work on it. I routinely package up material for a Python course I'm teaching into compressed tar archives. I host the compressed tar file on Google Drive, and use Shlink to create a shortened URL that can be downloaded and unpacked in Linux like this:
The use of the I'm running my Shlink server in a docker container on a Raspberry Pi, and it worked like a champ until I recently upgraded my client computer to Ubuntu 22.04. Now, when I run the command above in Ubuntu 22.04, I get this error:
If I replace the shortened URL with the raw (actual) URL, everything works:
When I Google the error message, there are some references to other applications having the same issue. In those cases, OpenSSL 3.0.x may have dropped support for legacy SSL handshakes, which leads to the error. Note: The links above are live and should work if you want to test them. Also, using Google Drive sharing links to download a file with something like Current behaviorAttempting to use Expected behaviorShortened links would download. How to reproduceUsing the |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Thanks for the kind words 🙂 I'm afraid this has nothing to do with Shlink, as it does not handle the encryption. I suppose the problem is on the certificate being configured on the reverse proxy in front of Shlink. |
Beta Was this translation helpful? Give feedback.
-
Ah! Thank you. My apologies. This makes sense. My certificate appears valid, but you've given me a good starting point for troubleshooting :-) |
Beta Was this translation helpful? Give feedback.
Thanks for the kind words 🙂
I'm afraid this has nothing to do with Shlink, as it does not handle the encryption.
I suppose the problem is on the certificate being configured on the reverse proxy in front of Shlink.