Webdav: Maximum backoff reached

CLI: duplicacy_win_x64_2.2.3.exe
OS: Windows 7 x64
service: yandex disk
protocol: webdav
init command is ok, but when i’m trying to make actual backup:
duplicacy.exe -debug -log backup -stats

A couple of chunks are uploaded, but process ends with this:

2019-10-16 14:52:54.605 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 15:04:10.964 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 15:15:30.272 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 15:26:50.068 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 15:38:18.297 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 15:49:43.565 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 16:01:27.492 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 16:13:46.034 TRACE WEBDAV_RETRY URL request 'PUT chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269' returned an error (Put https :// webdav .yandex .ru/b/docs_new/chunks/c0/226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: EOF)
2019-10-16 16:15:10.940 ERROR UPLOAD_CHUNK Failed to upload the chunk c0226a6d6367143369070dba78edccbc1b32be90c48e2f27ea0b9cb89f979269: Maximum backoff reached
2019-10-16 16:15:10.956 INFO INCOMPLETE_SAVE Incomplete snapshot saved to d:\docs/.duplicacy/incomplete

This is likely a yandex issue. Are you still experiencing it now?

Yes, there have been some events indicating that the yandex changed something on their side.

I had this too (using docker container in a Linux VM). After this error happend I was unable to start the backup again - immediatly got this error again.

Testing the webdav I figured out, that they changed the cert and the one stopped working at that time the error happened (0 o’clock).

Could fix it by restarting the container. Seems the cert was cached.