Rsync via SSH dosen't work anymore - libcrypto.so.3

Rocky Linux 9.5, fully updated

Hi Folks,
I cant sync my server backups anymore with my server at home.
Until the 18th of January it worked fine.

Now I get this Error:

rsync server to home
rsync: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(228) [sender=3.2.3]
Rsync failure. Backing off and retrying...

Line from the script:
sudo -u backupserver rsync -rtv --progress -e “ssh -p 25000” /backup/ backupserver@desination.domain.tld:/hdd/backup_server/

But libcrypto.so.3 is there!

ldd /usr/bin/rsync
        linux-vdso.so.1 (0x00007ffd8ab8c000)
        libacl.so.1 => /lib64/libacl.so.1 (0x00007fe20fa5c000)
        libpopt.so.0 => /lib64/libpopt.so.0 (0x00007fe20fa4d000)
        liblz4.so.1 => /lib64/liblz4.so.1 (0x00007fe20fa29000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007fe20f952000)
        libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007fe20f400000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fe20f000000)
        libattr.so.1 => /lib64/libattr.so.1 (0x00007fe20f948000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fe20f92e000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fe20fb0d000)
ls -lha /lib64/libcrypto.so.3
lrwxrwxrwx 1 root root 18  2. Nov 11:03 /lib64/libcrypto.so.3 -> libcrypto.so.3.2.2

ls -lha /lib64/libcrypto.so.3.2.2
-rwxr-xr-x 1 root root 5,2M  2. Nov 11:03 /lib64/libcrypto.so.3.2.2

On 15th of January there was a news about a rsync error, and we should update sync.
May this updates couse this error?
Anyone else run into this?
How should I fix it?

So it’s a script? Have you tested it direct on command line?
There was a recent update
3.2.3-20.el9, 3.2.3-20.el9_5.1
but I’m still on the old one.

Sure I did, same error.

Do the rsync versions match up on BOTH systems?
Also, can you SSH using that port to your home machine?

Yes, SSH into server @home works.
Also syncing the backup using the Virtualmin SSH Backup destination works.
The script worked fine until 18th.

rsync @home? Wait… is the command exetuing rsync @home, not on the server on the internet?

OMG rsync @home was broken (Debian 11)
Thx!

But I dont understand why it was executed at all?
Dosent rsync -rtv --progress -e “ssh -p 25000” “just” uses local rsync with SSH as a kind of transport?

In my experience, if a problem exists with rsync and it requires an update, then you often need to update it on both ends of the stream. rsync over ssh still uses rsync on both ends I believe. I use rsnapshot for backups, which uses rsync over ssh and it does require rsync on both ends.