Pcloud and Duplicati

It will be part of the next beta+stable release.

Duplicati is pretty picky about correct remote storage. From the screenshot it appears that the error is intermittent, because the next backup will not be allowed to run if there are files missing?

My guess is that this is caused by pcloud being eventually consistent, so it takes a while before the uploaded files are reported in the file list. This causes Duplicati to give error messages, because it really expects files that uploaded to stay in place.

Thank you for your response. I took a closer look at the history, especially the remote one.

Here is an example of a specific error:


Is it possible that the “list” operation to check file presence is performed too quickly after the “put”?
Would it be possible to introduce a delay between the “delete” and the final “list” query?

This issue is puzzling because some other backups run just normally…

Sorry I’m on my phone for now but if you want I can give more details logs when I’m back on a computer.

Hi, @Gekko thanks for the report. What is the remove volume size you have configured?

I am going to pursue the theory that the List might take longer to reflect changes after a larger file has been upload.

Are you using global or eu storage on pcloud?

Hello,

I left the default option of 50 Mo

I’m not sure it’s related to file size because the backup that fails most often is only a few hundred KB, while the other backup, which has never failed, is more than 200 MB. Moreover, another backup of nearly 5 GB, scheduled for weekly execution, also runs without any issues.

I’m using EU storage.

I fear that the webDAV interface from pcloud died for good… I have not been able to backup for quite a while now…

@kenkendk do you have any plan on moving the support to the native pCloud backend to the beta releases? I this is proving too unstable I might consider a different cloud provider…

@gabelach FYI: The v2.1.0.3_beta_2025-01-22 already includes native pCloud backend.

really? I must have missed it… and I am even executing that version
should I find it in the list of supported proprietary destinations?

version

immagine

destination list

My bad. I checked the source code and pCloud native source is included already in the bundle but not enabled. Lets wait for @kenkendk 's input on when it will make to beta.

no worries! thanks a lot for the quick reply!

1 Like

My thinking was that I did not want to delay the beta/stable release if we discovered some issue with a new backend, so it was not included in the beta.

We are working on the 2.2 release now, but I do not yet have a target date for that release. If you need the pCloud backend, you can try out the 2.1.0.108 canary build.

We really appreciate it if you can try the pCloud destination out before we move it to a stable release. There are currently no steps required to switch between the stable and the canary build, so you can download a zip package of the canary and run it locally without messing with your regular installation.

1 Like

Hi! Thanks a lot for the reply!
I downloaded the ZIP of the canary build and I will be trying it for the next days.

At the moment it seems to be working pretty well.

With the first backup I got only these warnings:

warnings

but I think that they are most probably connected to previous uploads via webDAV, which were not always successful. Could it be?

Yes, that looks like incomplete files.

I have installed version 2.1.0.110_canary_2025-02-28 on my windows 10 PC.

I could initially not get a succesfull connection to pcloud. Pressing the ‘test connection’ button when defining a backup would give the following error message popup:

HTTP failure response for http://localhost:8200/api/v1/remoteoperation/test:500 Internal server error
I had eapi.pcloud.com as the server, and the AuthID for my pcloud account.

I was about to give up but noticed a '‘Revert to NGAX client’ button. Pressed it and the old UI popped up.

Entered the same server and AuthID as before, and success! I have connection to pcloud, and the first backups have run succesfully as well.

I noticed in the old interface there was a drop down list for ‘Storage type’, set to pCloud (Native API). This field was not present in the new interface.

So, pCloud native connection works for me in the old interface, but not in the new one. It would be great if this could be solved.

Thanks for reporting @fabroom . I’ve confirmed the UI issue and opened an issue for it.

1 Like