Is there a way to check the size of a folder on pCloud?

Thanks

I've been informed by pCloud support that access to a number of API method calls (e.g. collection_list) has been removed. This has been effected by disabling username/password authentication. OAUTH2 authentication can be granted but is also blocked for these method calls.

The methods that still support authentication are related to file operations (e.g. uploadfile), which is why applications like rclone will continue to work.

So, if you are having problems getting your pCloud app to work, this could be the cause.

I'm a new client and seeding (uploading) data for the first time. I noticed uploads had been stuck for a few hours and, suspecting internet related issues, did some investigation. When that didn't yield anything I rebooted ... Uploads are now continuing.

I was wondering how pCloud uploads to their servers? What Windows services are used? What can I check to see if it's client side that's causing the problem? How to restart pCloud without a reboot (do I just quit the tray icon or is there more)?

Thanks for the help

I want to support pCloud, but uploading (either via a browser or via the MacOS app) is like dial-up internet speed.

My upload to Google Drive was around 8MB/sec. Meanwhile pCloud is, at times, 32KB/sec and 1MB/sec at absolute best (very rarely).

This has been the case for me generally for several years, both in Australia and when traveling abroad.

Hello,

For several years I've been using pCloud on my Google TV Chromecast via the Kodi plugin found on internet. For the past few weeks, the plugin has stopped working, so I've been looking for another solution. I managed to configure WebDAV access to my pCloud account from Kodi natively (without a plugin).

However, I'm having a problem: playback works for 10 seconds, then freezes for a few seconds, then resumes for another 10 seconds, and then freezes again. I suspect it's related to the cache size. I tried increasing the cache size in the Kodi settings to 128MB or 256MB (instead of 20MB), but it didn't improve things.

Does anyone have any idea what the problem might be? I can send screenshots of my Kodi settings if needed.

Thanks in advance for your help!

I got this when I tried to open a shared link. FYI, the contents are around 250 gb. Any help would be appreciated.

When it comes to backup systems i like to test it .
I have an "for life" account on pcloud and i suddenly realized an issue about sharing.
Lets say i wanted to test public sharing option.

I place a music/video and i use another of my own emails to test /share .
My pcloud email and name could be johnd , i use jdoe to share.
Legal its is ok because its my own emails and i have bought the video, but i have a naggin feeling that pcloud and other services think that an illegal shareing?

Now i know i would not do it, but in general to share it with or to other emails should not by itself be illegal.

I mean if i have pc and ipads..i could use different emails .

And if you ask there could be various reasons for not loggin in to pcloud account.

pCloud down?

I like pCloud overall, especially the lifetime plans and media features, but I still think end to end encryption should be included by default instead of being a paid add on.

Nowadays privacy is one of the biggest reasons people choose cloud storage. Services like Internxt, Mega, Filen already focus heavily on encrypted storage as part of the main experience.

Would you prefer slightly higher pricing if pCloud included full encryption for everyone by default?

For anyone else seeing pCloud uploads stuck recently: I noticed a few days ago that all of my uploads had stopped moving. Nothing was completing, and the upload queue just kept retrying.

I checked with a few other people and a friend also mentioned they had found a FB post about expired TLS certificates on some pCloud servers as they were seeing the same thing. So I started digging through the pCloud debug logs,

What I found is that the desktop client appears to be failing during TLS negotiation with some of the upload/checksum endpoints. In the logs, the pattern looks like this:

pssl-wolfssl.c:204 (function psync_set_ssl_error): got error -151
pssl-wolfssl.c:361 (function psync_ssl_connect_finish): returning PSYNC_SSL_FAIL
pnetlibs.c:1631 (function psync_net_get_checksums): assertion unlikely_log(!http) failed
pnetlibs.c:2248 (function psync_net_scan_file_for_blocks): assertion unlikely_log(rt==-2) failed
pupload.c:1722 (function task_run_upload_file_thread): Upload task failed

The important part is:

got error -151
returning PSYNC_SSL_FAIL

pCloud appears to use wolfSSL internally, and wolfSSL error -151 corresponds to a certificate date/expiry problem. In plain English: the client is trying to connect securely, but the server certificate appears to be invalid because of its date.

In my logs, the failures were happening against hosts like:

j2196.pcloud.com
j2203.pcloud.com
j2209.pcloud.com

This is the output from a script I wrote to parse the pCloud debug log and look at the certificate date of any pCloud hostname found:

hostname               certificate_expiry_utc   expired  days_until_expiry
---------------------  -----------------------  -------  -----------------
binapi.pcloud.com      2027-02-11 15:40:47 UTC  NO       276                     
binapiwas1.pcloud.com  2027-02-11 15:40:47 UTC  NO       276                     
j2196.pcloud.com       2026-02-27 13:50:03 UTC  YES      -74                     
j2203.pcloud.com       2026-02-27 13:50:03 UTC  YES      -74                     
j2209.pcloud.com       2026-02-27 13:50:03 UTC  YES      -74                     
j2210.pcloud.com       2026-02-27 13:50:03 UTC  YES      -74                     
j2214.pcloud.com       2026-02-27 13:50:03 UTC  YES      -74                     
j2218.pcloud.com       2026-02-27 13:50:03 UTC  YES      -74 

Notice the pattern? j####.pcloud.com hosts appear to be pCloud backend upload/checksum hosts used by the desktop sync client during file upload processing. When checking these hosts, the affected servers I tested all appeared to have the same TLS certificate expiry date: 2026-02-27 13:50:03 UTC

That would explain why uploads are stuck: the client is correctly refusing to continue when the secure connection cannot be validated. One possible reason some people are seeing this and others are not: it may depend on which backend upload/checksum endpoints your client gets assigned to. If the client lands on one of the affected `j####.pcloud.com` hosts, uploads may fail; if it lands on a different host with a valid certificate, uploads may continue normally. So this may look intermittent or account/system-specific even if the underlying issue is with a subset of pCloud’s backend endpoints.

To check your own logs, enable debug logging in pCloud, then look on your C drive for a directory called: C:\tmp

For whatever reason, at least on my system, pCloud does not appear to be writing this debug output to the normal Windows temp directory. Look under C:\tmp for a pCloud / psync debug log file, then search for:

PSYNC_SSL_FAIL
error -151
psync_net_get_checksums
task_run_upload_file_thread
Upload task failed

As far as I know, pCloud is aware of the issue. Now we wait for a fix.

I cannot prove with absolute certainty that the expired certificates are the root cause of everyone’s stuck uploads, but I strongly suspect they are involved. And even if this turns out not to be the only cause, pCloud seriously needs to update those certificates.

Letting backend upload/checksum infrastructure certificates expire is not something a cloud storage provider should be comfortable with.

To be clear, I am not saying anyone should disable certificate checks. You absolutely should not. Certificate validation is what protects you from connecting to the wrong server or having your traffic intercepted.

If others are seeing the same stuck-upload behavior, it would be useful to check your logs and report whether you see the same error -151 / PSYNC_SSL_FAIL pattern, especially against the j####.pcloud.com upload/checksum hosts.

Since I started backing my home dir (linux), pcloud started stalling almost daily. Too many files change in .config nad .local directories, and it was just getting stuck on files that disappeared or changed. I also had couple syncs (NFS mounts with 100k+ files (mostly because .git folders), that would confuse it occasionally).

Anyway, I switched to rclone backups (rclone sync) and syncs (bisync) and things are running smooth. Rclone can also encrypt files, which makes pcloud crypt service obsolete.

I am posting this to let people know that rclone solved all pcloud issues for me. Electron based apps are just not that great for some things.

I don't know what i am missing here: pCloud desktop client on both Windows 10 and Linux Mint. Both have the status icon on files and folders in the File Explorer missing.

And the only solution I can find online is to enable 'show the status' (or something similar) in the client's Settings->General.

Too bad, I don't have such option in settings. :-(

I have the status on OneDrive (Windows), and Mega (both Windows and Linux), but not in pCloud.

What am I doing wrong?

pCloud Drive version 2.0.4 on Linux, and 5.0.20 on Windows.

One of my xlsx file gets stuck in syncing. And it's the only one. Other files are synced just fine.

I restarted the computer, updated the pCloud drive to the latest version, all no luck.

And, the file is not in use by any other programs. Anyone has the same experience?

pcloud sync has been a reliable back up for my music work for some time. Not sure why, but it recently deleted all my local and cloud files. I successfully recovered it with rewind a few months ago after much work. I went to check it today, only to find it all gone again with no rewind option and nothing in the recycle bin.

I ran out of space, ordered a hard drive, and once it came I discovered I'm locked out. Now I have to pay them more just to get my own data?
Screw this company.