pCloud using WebDAV could not be authenticated because of server problems

I’ve been running into this error intermittently while using Cryptomator with pCloud via WebDAV.

The error can appear at any time: when I am opening the vault, opening files, or uploading new ones.

I will wait 5 seconds, try again, and everything works. Then a short time later the error appears once more.

Below us a link to my logs. Help me out?

https://ufile.io/tvq2g

Thanks for your feedback!

Hmm at the beginning of my test, I got the same behavior: occasionally authentication errors like the one from your log file:

D	20180308141040.447	OkHttp	<-- 401 Unauthorized https://webdav.pcloud.com/[_path_] (411ms)
D	20180308141040.448	OkHttp	Date: Thu, 08 Mar 2018 20:10:41 GMT
D	20180308141040.449	OkHttp	Server: Apache/2.4.10 (Debian)
D	20180308141040.450	OkHttp	Keep-Alive: timeout=5, max=98
D	20180308141040.455	OkHttp	Connection: Keep-Alive
D	20180308141040.463	OkHttp	<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>401 Unauthorized</title>
</head><body>
<h1>Unauthorized</h1>
<p>This server could not verify that you
are authorized to access the document
requested.  Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
<hr>
<address>Apache/2.4.10 (Debian) Server at webdav.pcloud.com Port 443</address>
</body></html>

After a few minutes the error is gone so I’m not able to reproduce it anymore.
Is it the first time that you’re facing this issue or does it often occur? Maybe they have server problems but I will check that later again.

Today I’m facing the same problem. Will dive deeper into that to figure out what is really happening.

Checked it already with some other cloud providers using WebDAV without any problems…

Increased the logging verbosity but since today, I’m unable to get this error happen anymore. It looks for me that they have solved server issues.
@8n2cij do you get any errors right now?

I no longer seem to be getting the same errors. Hoping it was a glitch on their part. Thank you very much for looking into it :slight_smile: