← Back to team overview

duplicity-team team mailing list archive

Re: [Question #248020]: WebDAV "SSLError: The read operation timed out" on goneo.de

 

Question #248020 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/248020

Description changed to:
Hi
I'm trying to back my stuff up to my goneo.de clound (german site) with WebDAV from my FreeNAS. I get the SSLError at 5 attempts and then it aborts. This is the debug log:

Using archive dir: /root/.cache/duplicity/fd782457b1febd1d5dc2bce83bb8720a
Using backup name: fd782457b1febd1d5dc2bce83bb8720a
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.ftpsbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Using WebDAV protocol http
Using WebDAV host cloud1.goneo.de port None
Using WebDAV directory /share/
Main action: full
================================================================================
duplicity 0.6.23 (January 24, 2014)
Args: /usr/local/bin/duplicity full --ssl-no-check-certificate -v9 /media/Pictures/Random/ webdavs://user:password@xxxxxxxxxxxxxxx/share/
FreeBSD duplicity 9.2-RELEASE-p4 FreeBSD 9.2-RELEASE-p4 #0 r262572+36f49d3: Fri Apr 18 04:16:22 PDT 2014     root@xxxxxxxxxxxxxxxxxxx:/home/jkh/9.2.1-BRANCH/freenas/os-base/amd64/tank/home/jkh/9.2.1-BRANCH/freenas/FreeBSD/src/sys/FREENAS.amd64 amd64 amd64
/usr/local/bin/python2.7 2.7.6 (default, Feb  6 2014, 13:32:45)
[GCC 4.2.1 20070831 patched [FreeBSD]]
================================================================================
Using temporary directory /tmp/duplicity-Q8YryV-tempdir
Registering (mkstemp) temporary file /tmp/duplicity-Q8YryV-tempdir/mkstemp-DMKGHr-1
Temp has 765166151680 available, backup will use approx 34078720.
Listing directory /share/ on WebDAV server
WebDAV create connection on 'cloud1.goneo.de' (retry 1)
WebDAV PROPFIND /share/ request with headers: {'Connection': 'keep-alive', 'Depth': '1'}
WebDAV data length: 0
WebDAV response status 401 with reason 'Unauthorized'.
WebDAV retry request with authentification headers.
WebDAV PROPFIND /share/ request2 with headers: {'Connection': 'keep-alive', 'Depth': '1', 'Authorization': 'Digest username="xxx", realm="ajxp_webdav_realm", nonce="5362cbd2e5f41", uri="/share/", response="4affe83e7f5aa0faae7b5c32a456d58a", opaque="df58bdff8cf60599c939187d0b5c54de", algorithm="MD5", qop=auth, nc=00000001, cnonce="5423e456536ee616"'}
WebDAV data length: 0
WebDAV response2 status 200 with reason ''.
Attempt 1 failed. SSLError: The read operation timed out
Backtrace of previous error: Traceback (innermost last):
  File "/usr/local/lib/python2.7/site-packages/duplicity/backend.py", line 344, in _retry_fatal
    return fn(self, *args)
  File "/usr/local/lib/python2.7/site-packages/duplicity/backends/webdavbackend.py", line 297, in _list
    raise e
 SSLError: The read operation timed out


The strange thing is that WebDAV works on my owncloud running on my NAS, but when I try this for goneo I keep getting this. Yes, I did try without --ssl-no-check-certificate and even with pointing to the cacert.pem file located at /etc/duplicity/. 
The even stranger thing is that it works fine on folderSync on my phone when I setup a WebDAV account with the exact same information as above. I don't even have to hit the "accept self signed certs". 
A friend of mine set this up on his VM and he gets the exact same error. 
I hope that you can tell me what's going on here. As far as I can say the error is with duplicity and not with me/us/goneo. Any help is much appreciated!!

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.