Uploaded file but failed to store EOF

[Arty.R]

Yes - Synology. It’s a trouble ? ) Another job backup to this SFTP stored without error.
I was completely delete the job, and start back up again. About 8 hours remaining )

[saspus]

Yes - Synology. It’s a trouble ? )

Welcome to the club Synology modified their SSH/SFTP server so it does not exactly conform to what’s expected of it.

The quick fix would be to add another / after your URL; e.g. sftp://user@synobox.local//Backups/Duplciacy

Don’t delete the job, just modify the URL everywhere. you find it (don’t remember exactly where web-ui stores it; but duplciacy CLI expects it in preferences file)

[Arty.R]

Synology modified their SSH/SFTP

I don’t know about it

Don’t delete the job, just modify the URL everywhere.

Too late - I already deleted it

I correctly understood that instead of now

sftp://arty@xx.xx.xx.xx:2222/duplicacy/backup

I should have

sftp://arty@xx.xx.xx.xx:2222//duplicacy/backup

in web it’s stored in json file

[saspus]

Synology modified their SSH/SFTP

I don’t know about it

I agree, that is not ideal. Here are prior discussion on this::

Chunk uploading error with Synology

This is a Synology issue. They run a modified version of ssh server so its behavior is kind of non-stardard/weird. My proof is that if sftp://server/Backups/duplicacy were the wrong path, you would have gotten an error when trying to download the config file before getting to the chunk uploading step. The chunk uploading error you got indicated that Duplicacy had already successfully downloaded the config file and the last snapshot, so the path must be right. The error itself I suspect was c…

Chunk uploading error with Synology

A chunk path in your case is Backups/duplicacy/chunks/64-byte-hash while the path of the config file is Backups/duplicacy/config. I first encountered this issue when developing Vertical Backup which is written in Python so I’m pretty sure this is limited to Synology only. Besides, rclone users ran into this as well: https://github.com/ncw/rclone/issues/1474 (and there it was a Duplicacy user who first found out the trick of using a single slash). Sadly I can’t think of a better solution than …

I should have

sftp://arty@xx.xx.xx.xx:2222//duplicacy/backup

in web it’s stored in json file

Yep.

[kevinvinv]

I have about 5 users backing up to my Synology via SFTP. Only one local computer has a problem.

It has gotten better with the latest version of Duplicacy… I think maybe there are retries now implemented in the code which probably helps.

[Arty.R]

Three different tasks completed successfully and without errors after adding to the path “/”. I think this solution need add to FAQ for Synology users.
Path stored in duplicacy.json file and after make change in path - the program must be restarted for reload settings.

[saspus]

I’m glad it worked!

I think this solution need add to FAQ for Synology users.

It is actually mentioned here:

Supported storage backends

Note for Synology users
If the SFTP server is a Synology NAS, it is highly recommended to use the absolute path (the one with double slashes) in the storage url. Otherwise, Synology’s customized SFTP server may terminate the connections arbitrarily leading to frequent EOF errors.

[akvarius]

I have experienced a similar problem with another SFTP server as well (freeftpd via VPN connection). I don’t remember now if it was the exact same problem, but the solution was the same .