Hi,
I was having the same problem and I found a workaround.

I am doing backups via ssh to a server running in my network. As I am using a 
special user on the server I added a host config in my .ssh/config file 
specifying the username IdentityFile and more to ease up access to the backuped 
data. The host is simply called "backup" but the actual hostname is different 
than that. Yet with ssh I am able to simply access my backup server by doing a 
"ssh backup" and this is also what I am using for the backup configuration in 
deja dup. Server name is "backup" which gives me passwordless access to the 
backupserver for the deja dup backup. And this also works perfectly for manual 
backups. However I was always getting the "Scheduled backup delayed" message 
for automatic schedules. 
I have now simply added an entry to my /etc/hosts with the backup server IP and 
"backup" as hostname. Now the "Scheduled backup delayed" is gone and all is 
working.

Does anyone having this problem also have a special config similar to
mine?

@Michael: Maybe with this you might be able to reproduce the problem on
your side.

/schaze

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982316

Title:
  Deja Dup is unable to detect network connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/982316/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to