Fix pCloud Authentication Errors — NetDrive
Troubleshoot pCloud login failures in NetDrive: wrong region servers, stale OAuth tokens, and accounts created without a native pCloud password.
A pCloud drive that connected without issue on setup day suddenly starts rejecting the login, or a brand-new connection fails with an error that just says the credentials are invalid even though the same password logs into pCloud’s website fine. Both symptoms trace back to a small set of causes specific to how pCloud accounts and regions work, and none of them mean the account itself is broken.
Mount pCloud the Right Way
NetDrive lets Google Drive, OneDrive, S3, SFTP, WebDAV and more appear as native drives on Windows and macOS — no syncing, no full downloads.
- Works with both pCloud US and Europe accounts
- Background uploads keep large files moving without blocking the drive
- Available on Windows, macOS, and Linux
Free trial. Lifetime and subscription plans available.
Map Your Symptom to a Cause
Before changing any setting, identify which one matches:
| Symptom | Most likely cause |
|---|---|
| ”Invalid credentials” on a brand-new connection, password is definitely correct | Account registered in the wrong pCloud region |
| A previously working drive suddenly asks to log in again | An expired or revoked session, unrelated to the password |
| Login fails with no clear error, account was created via a social sign-in | No native pCloud password ever set on the account |
NetDrive has supported pCloud since version 3.16.589 (March 2022), and all three of the causes above sit on pCloud’s side of the connection rather than in NetDrive itself.
Fix 1: Confirm the Account’s Region
pCloud runs two separate storage regions — United States and Europe — decided at signup and tied to the datacenter the account’s data physically lives in. A pCloud account created in one region authenticates against that region’s own servers, and entering perfectly correct credentials against the wrong region reads back as a generic invalid-credentials failure rather than anything mentioning “region.”
Check which region an account belongs to by signing into pcloud.com directly — the region is usually visible in account settings or in the URL pCloud redirects to after login. If NetDrive’s pCloud connection doesn’t ask for a region during setup, remove the drive and add it again through Add a Drive → pCloud, watching for a region selector in the login step before entering credentials.
Fix 2: Re-Authenticate After a Session Expires
pCloud sessions can be invalidated from pCloud’s own side — a password change, a security review that revokes active sessions, or simply a token reaching the end of its life. When that happens, NetDrive’s saved login stops working even though nothing changed in NetDrive.
- Open Drive Manager and select the pCloud drive.
- Click Edit, then Connect again to trigger a fresh login.
- Complete the sign-in flow pCloud presents, including any two-factor prompt if the account has it enabled.
If re-authenticating through Edit doesn’t produce a fresh login prompt, remove the drive entirely and add it again from scratch — a clean re-add avoids any leftover session state from the expired connection.
Fix 3: Set a Native Password on Social-Sign-In Accounts
pCloud accounts created through a Google or Apple sign-in don’t necessarily have a traditional pCloud password attached — the account exists, but there’s no password for a third-party client like NetDrive to authenticate with. Signing into pCloud’s own web app hides this because the browser session handles the social login directly; NetDrive can’t do that.
The fix happens entirely on pCloud’s side: sign into pcloud.com with the same Google or Apple account, go to account security settings, and set a password if one isn’t already configured. Once that’s done, use the email address and the new password (not the social sign-in button) when adding the drive in NetDrive.
When None of These Apply
If the region is confirmed correct, the session was freshly re-authenticated, and the account already has a native password, double-check for a typo in the email address itself — pCloud’s login is case-sensitive on the password but the more common mistake is an old or secondary email address that isn’t actually tied to the account holding the files.
Wrap-up
Most pCloud authentication failures in NetDrive come down to region mismatch, an expired session, or a missing native password on a socially-created account — rarely a problem with NetDrive’s connection itself. For the initial setup this troubleshooting builds on, see Mount pCloud on Windows with NetDrive or Mount pCloud on macOS with NetDrive. If two-factor authentication is part of the picture, Fix Mega Two-Factor Authentication Errors walks through the same clock-drift and re-authentication logic that applies across providers.
— Morgan, NetDrive