Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] rsync-server

Featured Replies

  • Author
9 hours ago, floppy_bl said:

Problem was that the system share was not public

Can you explain exactly which setting you changed?

  • Replies 58
  • Views 16.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • You can add an infinite amount of keys. There is a loop which reads all of them: https://github.com/eea/eea.docker.rsync/blob/master/docker-entrypoint.sh   By that even SSH_AUTH_KEY_BAN

Posted Images

1 hour ago, mgutt said:

Can you explain exactly which setting you changed?

I did not change anything except of the path in your dry run command. When using mnt/user/Public for example it worked. By checking the shares I saw that the system share is non public. So my guess was that this can be the reason.

  • Author
On 1/16/2025 at 9:03 AM, floppy_bl said:

By checking the shares I saw that the system share is non public

I still don't understand what you mean by "public". Are you talking about the SMB settings? SMB has nothing to do with local paths.

 

I think it is because some paths in unraid are mounts. In this case it could be necessary to change the specific container path from "read" to "read shared" or "read slave".

33 minutes ago, mgutt said:

SMB has nothing to do with local paths.

Strange. It did not work with /mnt/user/system/ unless I switched share settings to public. But it doesn‘t matter anyway, I can now backup all the shares I need. ☺️

  • 1 month later...

Ich schreibe es hier noch mal rein.

Seit Unraid 7 kann ich den rsync Server nicht mehr nutzen.

 

Ich habe noch mal neue Schlüssel generiert, wie es bei dem Docker steht mit:

 

ssh-keygen -t rsa -b 4096

 

Dann habe ich den Schlüssel in dem Dockercontainer eingepflegt und den Container gestartet.

 

Vom Clientsystem versuche ich dann 

 

rsync --dry-run --itemize-changes --archive -e 'ssh -p 5533' [email protected]:/mnt/user/system/ /tmp


Und erhalte als Antwort:

 

[email protected]: Permission denied (publickey,keyboard-interactive).
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
root@openmediavault:~#

 

  • Author
On 2/17/2025 at 1:48 PM, BigChris said:

Ich habe noch mal neue Schlüssel generiert, wie es bei dem Docker steht mit:

 

ssh-keygen -t rsa -b 4096

Auf dem Client? Und der Public Key ist auch vom Client, von dem du dich verbindest?

 

Du kannst auch direkt eine SSH Verbindung versuchen und die Ausgabe mit -v erweitern:

 

ssh -v -p 5533 root@tower

 

Er zeigt dir dann an welche lokale Schüsseldatei er verwendet hat, um sich mit dem Server zu verbinden.

 

Ich habe zB gerade ganz frisch den Container installiert und einen SSH Key auf meinem Windows Client erzeugt. Auch das ging problemlos, um mich mit dem rsync server zu verbinden.

 

  • 3 months later...
On 1/17/2025 at 9:51 AM, mgutt said:

I still don't understand what you mean by "public". Are you talking about the SMB settings? SMB has nothing to do with local paths.

 

I think it is because some paths in unraid are mounts. In this case it could be necessary to change the specific container path from "read" to "read shared" or "read slave".

I had the same issue as him and for me it didn't work because I activated the exclusive shares option in the global shares setting. I can't see any of the exclusive shares and my system folder was on the cache pool exclusively.

Trying to setup an Rsync pull task on an openmediavault backup NAS with the Unraid NAS with this docker being the source but always get this error:


"Host key verification failed. rsync: did not see server greeting rsync error: error starting client-server protocol (code 5) at main.c(1863) [Receiver=3.2.7] ERROR: The synchronisation failed.
END OF LINE"

After some issues with the exclusive share setting I managed to set everything up on the server side (Unraid NAS) and the dry run command (rsync --dry-run --itemize-changes --archive -e 'ssh -p 5533' root@tower:/mnt/user/system/ /tmp) also works if I ssh into my openmediavault NAS and use it to try to reach the main Unrais NAS.

Anyone know what the issue might be and how to fix it? Thanks in advance.

  • 9 months later...

The Symbol URL are no longer valid. Please fix this in the Template.

webgui: rsync-server: Could not download icon https://upload.wikimedia.org/wikipedia/en/thumb/1/11/Newrsynclogo.png/220px-Newrsynclogo.png

This is valid but the Download failed to:

https://upload.wikimedia.org/wikipedia/fr/thumb/1/11/Newrsynclogo.png/200px-Newrsynclogo.png

This is valid and the Download working at the moment:

https://rsync.samba.org/newrsynclogo.jpg

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.