Duplicacy Web Edition 1.5.0 is now available

Announcement
#4

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

QNAP App - How to select my actual datafiles?
#5

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

#6

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…

#7

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

image
image1636×760 82.8 KB

#8

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!

#9

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.

#10

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

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

#11

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.

#12

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

#13

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?

#14

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

#15

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?

#16

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?

3 Likes
Please make the update process (Windows) smoother
#17

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

#18

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

#19

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

1 Like
#20

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

#21

My certificate was due for renewal today and Duplicacy Web didn’t pick up the change until I restarted the web service. I can add that as a task for the post-deploy process, but then I would still need to enter the password to unlock and allow the scheduled tasks to run. Ideally, DW would periodically check the cert and reload it as necessary.

I’ll start a new feature request thread.

1 Like
#22

Thank you for adding the external certificate support!

For anyone else having trouble with getting up and running with an external cert:

  • Ensure you have ~/.duplicacy-web/certs with rwx (700) permissions on the folder for the account running web
  • As noted, you need domain.crt and domain.key files, where domain is your FQDN (ex backupserver.example.com), both files should have rw permission on then (600)
  • Change the listening port and domain in the settings
  • If duplicacy-web wont start and youre trying to use port 443, edit the systemd service file to include the below line under [Service], this will allow it to bind to a privileged port. Or use 8443.
    AmbientCapabilities=CAP_NET_BIND_SERVICE
#23

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.