I can’t connect to pcloud via WEBDAV in Duplicati
I always get: Failed to connect: Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.
I can connect to WEBFAV via chrome browser…
Who can help me?
No guarantees. Pcloud’s web site doesn’t claim to have WebDAV, and they don’t seem to put much priority on the server, now running on Apache HTTP Server 2.4.10 from 2014 according to Netcraft.
Do you by any chance use two-factor authentication? That’s said to be not supported with WebDAV.
Because Chrome is not a WebDAV client, have you tried another WebDAV client, such as WinSCP?
Are you on Windows? Accessing WebDAV with Windows talks about it, but WinSCP has better logs.
Have you been able to actually find your intended Duplicati folder in Chrome? If so, note the URL it uses, and you probably need to put some of the rightmost parts of it in Duplicati’s Path on server.
What are you doing at the time? It’s best to try the Test connection button before trying a backup.
What URL is that at? It’s nowhere at pcloud.com that search engines can find. Anyway, nice to know.
Searching in their Twitter web did find a mention – and a complaint about the WebDAV/2FA.problem:
I use Duplicati with pCloud via webdav since two years without major issues.
Thanks for the input @T-6
So works lately? Are you using two factor authentication? That sounds like it’s guaranteed to not work.
I don’t know how exactly one has to fill in the “Path on server” for Pcloud, or if it has to be pre-created, however pre-creation seems less likely to have problems. Perhaps you can help @Alfred_Muhlleitner whenever this continues. I don’t have Pcloud, so can’t advise on where and how to create the folder…
which settings are you using?
Sorry, have not been here lately.
Server: webdav.pcloud.com
Port: 443
As I remember I used an existing folder for “Path on Server”
I am new to duplicati and have a fresh setup with docker.
I was trying to set this up with webdav lately, however it does not seem to work for me with:
I disabled 2FA for testing and still get a 401 - Unauthorized answer.
Can someone else still verify that this works and that it’s just me?
Thank you very much.
If your data are on a server in Europe, use
ewebdav.pcloud.com
1 Like
There is now a canary build with support for pCloud (without WebDAV):
It works by creating an access token, and then you can use that token without username/password and you can keep MFA enabled.
Note that due to the way pCloud is working, your WebDAV data and the new pCloud backend’s data are stored in different folders on pCloud.
2 Likes
This is really a nice coincidence! It seems that the ewebdav access to pCloud suddenly stopped last week (at least I cannot get it to work anymore) and I was just looking around for a solution.
Maybe I’ll give a try to this release
1 Like
@kenkendk Had pcloud tested a few yrs bck and couldn’t get it to work stable with Duplicati on webdav. After reading you’re getting an API-implementation (like rclone I guess) I’d like to give it another try.
'Cause I’d never change a running system 
… I’d like to set up the net8-canary in parallel to the stable running net4. Is this possible?
(In case this was already answered somewhere else, sorry, I haven’t found it)
Hi @Ralf, yes it is possible, but can be a bit tricky to pull off due to shared data.
Duplicati (any version) uses the same location for the database.
When you run a newer version, this database may be upgraded, making it difficult to go back.
You can run an isolated version of Duplicati if you give it the commandline argument --portable-mode. This will make it use a data folder in the same folder where the binary is stored.
You can then download the zip version, unpack it, and start it from the commandline with --portable-mode. This will allow two different versions of Duplicati to run at the same time (which can be confusing). The second instance will then choose a different port, most likely 8300, but you can specify it with --webservice-port=8300.
In case something goes wrong, the updated Duplicati will upgrade your databases, but leave a copy of the pre-upgrade databases in place so you can revert with few hassles.
Hi @kenkendk , didn’t know about portable-mode and will test it out asap. Thx a lot for the tip!
Hello,
I am currently testing version 2.1.0.100_canary_2024-11-25 (via the docker duplicati/duplicati:2.1.0.100 image) with pCloud and its native API.
On my end, I have never been able to get pCloud working correctly through WebDAV (see here: GitHub issue #5621).
I haven’t encountered any major issues, and the performance is good compared to WebDAV, which was very slow when it worked at all.
I ran several tests with different data samples.
It works well with token generation and MFA enabled.
The only issue I ran into was using a subdirectory structure. When entering the name of a folder (e.g., “test1”), it works fine.
It correctly uses (or creates if it doesn’t exist) the folder under “Application/DuplicatiBackup/test1” on pCloud, which is the required root folder via the native API.
However, I couldn’t find the syntax or figure out if it’s possible to use a subdirectory like “Application/DuplicatiBackup/test1/test2”.
I also have a separate question related to Docker: is it possible to use a secret for the SETTINGS_ENCRYPTION_KEY environment variable with Docker?
@marceloduplicati have you managed to get subfolders working with pCloud?
Not sure what you mean here. You can supply the environment variable via the Docker commandline (or Docker compose).
I’m talking about the possibility of using a Docker secret :
Like what linuxserver.io allows with their Duplicati Docker image.
GitHub - linuxserver/docker-duplicati
Duplicati does not directly support providing the secret from a file, which is the abstraction that Docker secrets use. But you can use the preload settings or the file-based secret manager as the source.
Using a preload file
To use the preload approach, prepare a preload.json file with something like this:
{
"env": {
"server": {
"SETTINGS_ENCRYPTION_KEY": "real encryption key"
}
}
}
Then set it up in the compose file:
services:
myapp:
image: duplicati/duplicati:latest
environment:
- DUPLICATI_PRELOAD_SETTINGS: /run/secrets/preloadsettings
secrets:
- preloadsettings
secrets:
preloadsettings:
file: ./preload.json
Using a secret manager
The secret manager can contain multiple secrets, including encryption passphrases, connection credentials etc. To set it up, create a secrets.json file such as this:
{
"settings-key": "real encryption key",
"ui-password": "real UI password",
"additional-key": "add more as needed"
}
Then set it up in the compose file:
services:
myapp:
image: duplicati/duplicati:latest
environment:
- DUPLICATI__SECRET_PROVIDER: file:///run/secrets/secretprovider
- SETTINGS_ENCRYPTION_KEY: "$settings-key"
- DUPLICATI__WEBSERVICE_PASSWORD: "$ui-password"
secrets:
- secretprovider
secrets:
secretprovider:
file: ./secrets.json
1 Like
Hello,
I have been testing version 2.1.0.101_canary_2024-12-06 since its release, and the subfolder feature is now working correctly.
Do you know if this feature will be implemented soon in the stable release?
I have been running several test cases, and everything works well overall. However, I occasionally encounter errors related to missing files:
2024-12-19 04:00:01 +01 - [Warning-Duplicati.Library.Main.Operation.FilelistProcessor-MissingFile]: Missing file: duplicati-20241219T030000Z.dlist.zip.aes
Since I am new to Duplicati, I am unsure of the cause of these errors and their potential impact on backups or the ability to restore data.