Webui restore: Failed to list the revisions: Error: timeout of 0ms exceeded

Support
#1

Hello, this is my first post on this forum as a kind-of-new Duplicacy user. My backups have begun to complete and I wanted to try the restore feature to see how that works.
However, none of my backups will show in the web.
What I do:

  1. Restore
  2. Select storage
  3. Select backup ID
  4. wait
    After about 2 minutes, I get the following error as a notification:
    Failed to list the revisions: Error: timeout of 0ms exceeded

After this notification, the message at the bottom still reads
Listing revisions of backup [backup ID name] in the storage

But even leaving that for an hour does not change anything, so I assume that nothing is actually happening.

My config:
Duplicacy web ui using Saspus docker image running in a LXC on Proxmox in my homelab backing up my private photo collection to Google Drive (gsuite). The web-ui is reverse proxied to my domain using nginx-proxy-manager.

Thanks in advance if someone would be so kind as to help me figure out what I have configured wrong.

#2

Listing the revisions should not be that slow. Can you post the relevant part of the log in ~/.duplicacy-web/logs/duplicacy_web.log?

#3

Hello, thanks for your reply!

I have just now gone through the steps again and this is what shows up, edited for privacy:

2019/10/14 14:21:57 192.168.1.15:39954 GET /restore
2019/10/14 14:21:58 192.168.1.15:39958 POST /list_repositories
2019/10/14 14:21:59 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.2.3 [-log -d info -repository /cache/localhost/all gcd://Duplicacy]
2019/10/14 14:21:59 Set current working directory to /cache/localhost/all
2019/10/14 14:22:07 DEBUG PASSWORD_ENV_VAR Reading the environment variable DUPLICACY_GCD_TOKEN
2019/10/14 14:22:15 DEBUG STORAGE_NESTING Chunk read levels: [1], write level: 1
2019/10/14 14:22:15 INFO CONFIG_INFO Compression level: 100
2019/10/14 14:22:15 INFO CONFIG_INFO Average chunk size: 4194304
2019/10/14 14:22:15 INFO CONFIG_INFO Maximum chunk size: 16777216
2019/10/14 14:22:15 INFO CONFIG_INFO Minimum chunk size: 1048576
2019/10/14 14:22:15 INFO CONFIG_INFO Chunk seed: 6475706c6963616379
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT[backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:16 INFO STORAGE_SNAPSHOT [backup-id-name-removed]
2019/10/14 14:22:22 192.168.1.15:39992 POST /list_revisions
2019/10/14 14:22:22 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.2.3 [-log list -storage duplicacy-lxc -id scan]
2019/10/14 14:22:22 Set current working directory to /cache/localhost/all
2019/10/14 14:22:22 INFO STORAGE_SET Storage set to gcd://Duplicacy

In the web-ui, the error is thrown at this point, but this does not show up in the log.