Duplicacy Web Edition 1.5.0 is now available

Download links:



  • Add options for RSA encryption and Erasure Coding when configuring a new storage
  • Accept custom HTTPS certificates placed under ~/.duplicacy-web/certs [1]
  • Fixed a bug in the include/exclude pattern set up dialog that caused some characters to be wrongly url-encoded
  • Fixed a bug where a deleted schedule causes other running schedules to never finish
  • Fixed the progress bar for check and copy jobs
  • Fixed mismatched graph colors
  • Don’t add -a to a check job if a backup id is already specified with the -id option
  • Add a date field when sending emails
  • Show the expiration date of lifetime licenses correctly (which never expire)
  • On FreeBSD fail over to our own keyring implementation if the default one is not available
  • Automatically skip files with the extended attribute com.apple.metadata:com_apple_backup_excludeItem for new backups on macOS [2]
  • Prompt for enabling Full Disk Access if not enabled on macOS
  • Set the number of threads to 4 for most cloud storages when adding a new backup job
  • Make the log viewer most responsive
  • Use https://duplicacy.com/latest_cli_version to find the latest/stable CLI version
  • Show the remote ip address in the log when an incorrect administration password is entered


[1] You’ll need to create 2 files under ~/.duplicacy-web/certs: domain.crt contains the full chain certificates and domain.key is the private key (domain should be replaced by the actual domain name).

[2] This is done by setting the preference key exclude_by_attribute to true in new backups created in 1.5.0, which means existing backups will not skip these files by default. If you want to change this behavior for existing backups, manually modify the preference key exclude_by_attribute in ~/.duplicacy-web/duplicacy.json to true.


Can the 1.5.0 linux executable replace the version in the QNAP qpkg?

on windows we get this on almost every operation:

Failed to download the CLI executable: Get https://github-production-release-asset-2e65be.s3.amazonaws.com/52319759/a187a880-2802-11eb-9785-25876443eb85?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210120%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210120T184144Z&X-Amz-Expires=300&X-Amz-Signature=480b444d9dbba711f985babe595876c4763b91dd4faeaf016320299ae3a2a2e3&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=52319759&response-content-disposition=attachment%3B%20filename%3Dduplicacy_win_x64_2.7.2.exe&response-content-type=application%2Foctet-stream: dial tcp connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

You can try 1.5.0 qpkg here:

Marvell ARM: https://acrosync.com/duplicacy-web/duplicacy_web_qnap_arm_x19_1.5.0.qpkg
Mindspeed ARM: https://acrosync.com/duplicacy-web/duplicacy_web_qnap_arm_x31_1.5.0.qpkg
Annapurna Alpine ARM: https://acrosync.com/duplicacy-web/duplicacy_web_qnap_arm_x41_1.5.0.qpkg
AnnapurnaLabs AL324 ARM 64bit: https://acrosync.com/duplicacy-web/duplicacy_web_qnap_arm_64_1.5.0.qpkg
Intel/AMD x86: https://acrosync.com/duplicacy-web/duplicacy_web_qnap_x86_1.5.0.qpkg
Intel/AMD 64bit: https://acrosync.com/duplicacy-web/duplicacy_web_qnap_x86_64_1.5.0.qpkg

I believe this was a temporary github issue. You can restart the web GUI to see if the CLI can be downloaded.

looks like it, but now it’s very slowly downloading and you learn this after you entered all your credentials… I understand and like the update mechanism but you should inform about this in the UI I think…

mh… not sure, what’s going on here, it’s like this for hours now:

I was able to get the custom certificates working. I at first missed that the “domain” was just a placeholder and should be replaced with the actual domain. Then I think I kept getting bitten by permissions. Setting the cert and key files to be 400 looked to be the final piece.

I do wonder though, will duplicacy-web pick up on files that have changed behind the scenes? (I’m using the Let’s Encrypt DNS renewal process.) Or will that require a manual restart?

Also, before I got the certs working, it looked like the HTTP server was still running as an immediate redirect to HTTPS. Now that I have the certs all set, it looks like the HTTP server isn’t up anymore. Is that intentional? I’d think the redirect would be desirable.

Thanks for another great release!

You can try to download the CLI executable manually from Releases · gilbertchen/duplicacy · GitHub and place it under ~/.duplicacy-web/bin.

I’m not sure what could cause the automatic download to fail, but it may be that github release file servers aren’t reliable in some regions. This issue had been reported before so it is not limited to 1.5.0 release.

ok, I am on windows, installed as a service, where to put the executable?

do you plan a fix? it’s a bit annoying…

Yes, this is intentional. Previously the HTTP server is required by Let’s Encrypt. The HTTP to HTTPS redirect would be convenient, but there is some risk with having port 80 open.

The home directory for a Windows directory is usually C:\ProgramData so you should put the executable under C:\ProgramData\.duplicacy-web\bin.

What is the procedure for updating from the 1.4.1 QNAP qpkg to the 1.5.0 qpkg? There’s no AppCenter Update option for manually installed qpkgs. Does one simply install 1.5.0 manually without removing 1.4.1?

this looks like a github issue, download speeds are abysmal: image

Got it. Sounds reasonable. I suppose if I really wanted a redirect I could start my own minimal server.

What about when the cert gets updated? Will the server notice the file has changed? Or will it need to be restarted to pick up the new cert?

Could you maybe explain how to update an existing install?

I have Duplicacy Web installed as a service, but if I try to update it by running the new installer again with -install-service, it installs, and then fails because “Service already exists”. The service still points to the 1.4.1 install though, which no longer exists, so now I also can not start the service any more.

Edit: Got it to work by first removing the service through
sc delete "Duplicacy Web Edition"
in cmd, and then installing the new version.

Edit2: My backup schedules which have been started by 1.4.1 are still running, but 1.5.0 does not see them, 1.5.0 tries to start a second instance of that backup schedule. So I probably have to manually kill the duplicacy_win_x64_2.7.2.exe which have been spawned by 1.4.1 in the task manager, and only after that let the schedule start again in 1.5.0?


I’m also interested and following if it’s safe to upgrade to the new version? I am, too, running Duplicacy as a service.

Anyone able to do this? My json doesn’t have the preference key ‘exclude_by_attribute’ after upgrading to 1.5.0

Solved it – just had to run a backup after upgrading. That populated the json with the key I could modify.

1 Like

Updating by manually installing the 1.5.0 qpkg without removing 1.4.1 was successful.