Linux Client not Working

URBackup 2.2.10 on OpenMediaVault. Client 2.2.6 (downloaded from server) on Ubuntu.

The client says “connected” on the server, but urbackupclientctl status shows:

“capability_bits”: 12,
“finished_processes”: [],
“internet_connected”: true,
“internet_status”: “connected”,
“last_backup_time”: 0,
“running_processes”: [],
“servers”: [],
“time_since_last_lan_connection”: 12103728548

When I try urbackupclientctl start -f I get:

Error starting backup. No backup server found.

Completely new installation. The backup server is working fine for WIndows clients.



Okay, got the same problem on Ubuntu. Have not found a solution yet, nor have had a response.

Going to troubleshoot some more and will inform you if I discover something.

Sorry you are having issues. To solve the problem the client (debug) log would be useful.
If possible, could you post it or send it?

This post describes how to change the client to debug logging, where it is stored and where to send it to if posting is not possible: Having problems with UrBackup? Please read before posting


Thanks for the reply.

Here’s what is happening:

First off, I’m using Ubuntu 18.04, which does not include the /etc/rc.local file, so the install instructions need revision for later versions of Ubuntu.

Second, the client backend “urbackupclientbackend” can start and run as a systemctl service, which runs as the root user, which causes the urbackupclientgui client shell command to prompt for the sudo password in order to enable the urbackupclientgui to setup paths. I can write a work around for this.

I have it working now, but the instructions are not accurate to this type of install, and I might add the admin documentation is not written at all well despite a likely well-intended effort. You can glean lots of things from it, but it is a seriously confusing document without good flow and outline.

Also, the URL “” looks like the markdown used to generate the HTML link for the admin manual states “PDF” but links to the HTML page where the PDF can be downloaded. Also very confusion. There are others, but I’ll stop here.

I do applaud the effort to build an open-source client/server system like this, it’s got awesome potential, but what makes or breaks such a great effort is having documentation that is far below the effort to create the system in the first place.

Bottom line is I have it working now.


How did you manage to get it working on 18.04?
Struggling here :frowning:

ok got the same problem, as David has described, on MX-Linux. The client can’t be discovered by the server, but the client says it’s connected to it. Is there any solution?

EDIT: Ok got the client working now. There were just some auth-issues I could solve. Found them through the log-files.