Unraid Backup to Windows Server - Signing Required Error

Support
#1

I did do a search on this, but don’t think it is root cause. Basically what I am doing is backup up from an Unraid share via Duplicacy to a Windows Server SMB share.

Duplicacy is running as a container on Unraid and seems to be functioning fine. It can access the source shares on Unraid and the SMB share on Windows without issue.

When I go and start the job, it quickly fails with the following:
invalid response error: signing required

Thinking is might be an issue with SMB signing, I have adjusted the SMB/Samba config within Unraid. It was already set to use SMBv2, but I also added the following settings:

min protocol = SMB2
Server signing = auto
Client signing = auto

Not sure exactly what this could be, but would appreciate any help anyone can provide. I am new to Duplicacy and in the trial period and am hoping to put this to bed.

Here is a log dump:

Running backup command from /cache/localhost/0 to back up /backuproot/Data
Options: [-log backup -storage Unraid -threads 1 -stats]
2025-04-21 16:58:13.374 INFO REPOSITORY_SET Repository set to /backuproot/Data
2025-04-21 16:58:13.375 INFO STORAGE_SET Storage set to smb://admin@192.168.1.217/D/Backup
Creating directory snapshots/Data/
2025-04-21 16:58:13.388 INFO BACKUP_START No previous backup found
2025-04-21 16:58:13.499 INFO INCOMPLETE_LOAD Previous incomplete backup contains 97517 files and 134 chunks
2025-04-21 16:58:13.499 INFO BACKUP_INDEXING Indexing /backuproot/Data
2025-04-21 16:58:13.499 INFO SNAPSHOT_FILTER Parsing filter file /cache/localhost/0/.duplicacy/filters
2025-04-21 16:58:13.500 INFO SNAPSHOT_FILTER Loaded 0 include/exclude pattern(s)
2025-04-21 17:00:29.359 ERROR UPLOAD_CHUNK Failed to upload the chunk b0886a743255b5b627d2b1930cc282abe0def5c32319d81e3c8ec5ba08abab63: sync Backup\chunks\b0\886a743255b5b627d2b1930cc282abe0def5c32319d81e3c8ec5ba08abab63.tgwqqmch.tmp: invalid response error: signing required
2025-04-21 17:01:48.315 INFO INCOMPLETE_SAVE Incomplete snapshot saved to /cache/localhost/0/.duplicacy/cache/Unraid/incomplete_snapshot
Failed to upload the chunk b0886a743255b5b627d2b1930cc282abe0def5c32319d81e3c8ec5ba08abab63: sync Backup\chunks\b0\886a743255b5b627d2b1930cc282abe0def5c32319d81e3c8ec5ba08abab63.tgwqqmch.tmp: invalid response error: signing required
#2

Duplicacy uses its own SMB client implementation so samba settings on unraid won’t have effects.

It looks like it requests signing but it’s disabled on your server.

Check with (in power shell)

Get-SmbServerConfiguration | Select-Object RequireSecuritySignature, EnableSecuritySignature

I expect both will be false. You can then enable signing:

Set-SmbServerConfiguration -EnableSecuritySignature $true

(Note, the above is a result of googling, I don’t use windows, so it may not work as expected)

#3

Great thought and while it didn’t quite work, it put me on the right path. I was ultimately forced to disable the requirement of a security signature in order to get this to work using, although I did keep it enabled:

Set-SmbServerConfiguration -EnableSecuritySignature $true -RequireSecuritySignature $false

Thank you again for the response and pointing me in the right direction! Not sure I will keep it this way, but this is a thread I can pull on.

1 Like
#4

Oh, interesting, so the issue was the opposite: that signing was required by the server, but duplicacy wasn’t using it.

@gchen, should not duplicacy use signing, to guarantee integrity of data in transit to the sever?

#5

Agreed. The SMB storage backend is based on GitHub - hirochachacha/go-smb2: SMB2/3 client library written in Go., which provides an option for signing, but Duplicacy doesn’t enable it. I’ll run a test to confirm.

1 Like