The CLI executable is not available from github.com: Failed to download the CLI executable

Since this morning I can not execute any job in duplicacy.

The CLI executable is not available from github.com: Failed to download the CLI executable
wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen., exitCode: 0

Any ideas ? Never had that before. Double checked my fiewall and connectivity - no change to before where the problem did not occur.

Help !!! :slight_smile:

Hi all
Did some further investigation and found the reason. Yersterday evening I updated my win10 enterprise with two Microsoft updates. Then tonight the scheduled jobs failed with the following error message:

The CLI executable is not available from github.com: Failed to download the CLI executable: read tcp 10.0.0.21:49682->52.217.64.76:443: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.

I now de-installed the two Microsoft updates and now it is again running properly.

Would be nice if somebody can have a look at this - I assume thet the two MS Updates were some security patches coming along on patchday.

Regards Urmel

This may not be caused the Windows updates. There is a new CLI release on github.com and when the web GUI restarted it attempted to download the new CLI release but github.com is known to have network issues occasionally.

For the next web version I’ll make a change to fall back to the latest CLI release that has been downloaded before if the download from github.com fails.

I never had this issue before and I tried it today - after the windows updates. The error was persistent and a colleque of mine tried at the same time from a different machine wtihout this updates and was successful. Looking at the CVE message for the updates brought me to check if the de-installl would be successfull and it was. Maybe it is worth to have a closer look to that.

And by the way - if I can not execute my duplicacy jobs - I do not have backups - I can not wait until next version … :slight_smile:

@gchen if my understanding is correct, the CLI is downloaded only when the Web GUI starts. So if the download fails, there won’t be any retry until Web GUI so the computer is restarted, so there can be several days or weeks without a backup. I ran into this after 35 days without a backup :frowning:
This should realy be fixed asap!

This is happening to me on Mar 18, 2025. I just now configured Duplcacy with all the correct information but before I ran a backup, I rebooted my Ubuntu server. Then when I came back to the web browser, the error about the CLI executible being not available is preventing me from being able to do the first step of configuration (Storage Configuration). I have no idea what happened.

check duplicacy_web.log.

How are you starting duplicacy_web? Perhaps, when duplicacy starts, the network is not yet ready. If you are starting duplicacy with systemd – make the service depends on netwait, or at least, network availability. Otherwise, just restart it once after machine fully boots – it only needs to be able to download CLI once.

Thank you very much for this answer. I suspect you are on to something. I was actually quite confused about how to install Duplicacy on Ubuntu. I was trying to find an application to install using the apt repository installer. But it appeared that was not available. Then I found the web app and installed it.

I am going to try to recall now how I did that install and verify it is loading properly. I had thought that I had installed it. Then turned on the execute bits and then turned it into a service. But maybe it only worked until I rebooted the computer.

I am trying to find the instructions again.

In the downloads folder I have duplicacy_web_linux_x64_1.8.3
I have copied that file to /usr/bin/duplicacy-web and turned on the execute bits:

-rwxr-xr-x 1 root root 39233607 Mar 19 15:18 duplicacy-web*
scarney@250310-tower:/usr/bin$ ll dupl*

I also created a file called duplicacy-web.service

scarney@250310-tower:/etc/systemd/system$ ll dupl*
-rw-r--r-- 1 root root 152 Mar 19 15:24 duplicacy-web.service

Are those permissions correct? Is this enough to launch duplicacy-web each time the system reboots?

I know that I am not there yet. Because I am getting a failure when I try to verify the web service is running:

scarney@250310-tower:/usr/bin$ sudo systemctl status duplicacy-web
× duplicacy-web.service - Duplicacy Web service
     Loaded: loaded (/etc/systemd/system/duplicacy-web.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2025-03-19 15:52:28 CDT; 3min 32s ago
   Duration: 49ms
    Process: 25282 ExecStart=/usr/bin/duplicacy-web (code=exited, status=4)
   Main PID: 25282 (code=exited, status=4)
        CPU: 42ms

Mar 19 15:52:28 250310-tower systemd[1]: Started duplicacy-web.service - Duplicacy Web service.
Mar 19 15:52:28 250310-tower dbus-daemon[25297]: [session uid=0 pid=25295] AppArmor D-Bus mediation is enabled
Mar 19 15:52:28 250310-tower dbus-daemon[25297]: [session uid=0 pid=25295] Activating service name='org.freedesktop.secrets' reques>
Mar 19 15:52:28 250310-tower org.freedesktop.secrets[25299]: GNOME_KEYRING_CONTROL=/root/.cache/keyring-RO7T32
Mar 19 15:52:28 250310-tower dbus-daemon[25297]: [session uid=0 pid=25295] Successfully activated service 'org.freedesktop.secrets'
Mar 19 15:52:28 250310-tower duplicacy-web[25282]: Duplicacy Web Edition 1.8.3 (5A554A)
Mar 19 15:52:28 250310-tower duplicacy-web[25282]: Can't start the web server at 127.0.0.1:3875: listen tcp 127.0.0.1:3875: bind: a>
Mar 19 15:52:28 250310-tower systemd[1]: duplicacy-web.service: Main process exited, code=exited, status=4/NOPERMISSION
Mar 19 15:52:28 250310-tower systemd[1]: duplicacy-web.service: Failed with result 'exit-code'.

BTW, I am able to bring up Duplicity in the web browser at http://127.0.0.1:3875/

I have this write up from my Synology days: Duplicacy Web on Synology Diskstation without Docker | Trinkets, Odds, and Ends. Synology used upstart back then. Now they use systemd, like Ubuntu does, and one of the blog guests posted config for systemd in the comments. You would need to click to load disqus comments there, I don’t load them by default, because tracking.

This is probably coz you already have the duplicacy process already running, though not as a service (or maybe accidentally under a different service name?), so it’s trying to start but exiting as the port is already used.

I’d try to figure how it’s already running (cron?):

ps -efH

Also, when I forget to document how I did something before: :slight_smile:

history | grep duplicacy

How does your /etc/systemd/system/duplicacy-web.service compare to this:

[Unit]
Description=Duplicacy Backup

[Service]
User=duplicacy
Group=duplicacy
Environment="HOME=/home/duplicacy"
WorkingDirectory=/home/duplicacy
ExecStart=/home/duplicacy/bin/duplicacy_web
Restart=on-failure
RestartSec=30

[Install]
WantedBy=multi-user.target

(You might be using somewhere like /opt tho so the exact paths will vary - so long as they match up with your own and the permissions are correct.)

Thanks Droolio,

One big difference is that I did not create a separate duplicacy user and group.

I also saved the working directory as /usr/bin/
with the ExecStart as /usr/bin/duplicacy_web

This is how it appears when I put in ps -efrH
root 1957 1 0 17:39 ? 00:00:00 /usr/bin/duplicacy_web

When I ran ps -efH, I did not see more than one instance of duplicacy running. But, maybe it is and I am not understanding.

I have not placed anything in the crontab for duplicacy.

Ah nevermind. The main thing to look out for was the third column which is the parent process ID, which there is none in this case, so doesn’t tell us much. Except that it’s running as root.

Try kill the running process then start the service:

kill 1957
sudo nano /etc/systemd/system/duplicacy-web.service     #edit as necessary
systemctl daemon-reload            #important if you edit the service file
systemctl start duplicacy-web

Hopefullt it should stay up, as the port shouldn’t be locked. Later you may have to test what happens after a reboot; is it the systemd service starting up or by some other method.

I was able to set up my system service configuration to match the reply from @Droolio and was able to get beyond the error messages. I still have not actually gotten the backup to run but will open a new thread rather than continue here since we seem to have received some very good answers here about the subject of this thread.

I am adding a comment here to state that I believe the secret to this working for me was when I created the User:Group of duplicacy:duplicacy