I can't connect to proton drive

STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.

What is the problem you are having with rclone?

Hello,

I don't understand, I've been using rclone for years with other providers but I can't connect to proton drive.

Run the command 'rclone version' and share the full output of the command.

./rclone version
rclone v1.66.0

  • os/version: debian 12.5 (64 bit)
  • os/kernel: 6.1.0-20-amd64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.22.1
  • go/linking: static
  • go/tags: none

Which cloud storage system are you using? (eg Google Drive)

proton drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

./rclone lsl protonrc:
2024/05/07 15:31:39.746936 WARN RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401), Attempt 1
2024/05/07 15:31:39.746995 ERROR RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401)
2024/05/07 15:31:40.083762 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422), Attempt 1
2024/05/07 15:31:40.083778 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422)
2024/05/07 15:31:42.137468 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4: Are you sure this is the correct domain? Please verify and try again. (Code=8002, Status=422), Attempt 1
2024/05/07 15:31:42.137493 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4: Are you sure this is the correct domain? Please verify and try again. (Code=8002, Status=422)
2024/05/07 15:31:42 Failed to create file system for "protonrc:": couldn't initialize a new proton drive instance: 422 POST https://mail.proton.me/api/auth/v4: Are you sure this is the correct domain? Please verify and try again. (Code=8002, Status=422)

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

/rclone config redacted
[backblaze]
type = b2
account = XXX
key = XXX
hard_delete = true

[google]
type = drive
client_id = 
client_secret = 
token = XXX

[kdrive]
type = webdav
url = https://connect.drive.infomaniak.com
vendor = other
user = XXX
pass = XXX

[protonrc]
type = protondrive
username = xxxxx@xxxx.com
password = XXX
client_uid = 
client_access_token = 
client_refresh_token = 
client_salted_key_pass = 

[yandex]
type = yandex
token = XXX

[yandex-year]
type = yandex
token = XXX
### Double check the config for sensitive info before posting publicly

A log from the command that you were trying to run with the -vv flag

./rclone -vv lsl protonrc:
2024/05/07 15:40:03 DEBUG : rclone: Version "v1.66.0" starting with parameters ["./rclone" "-vv" "lsl" "protonrc:"]
2024/05/07 15:40:03 DEBUG : Creating backend with remote "protonrc:"
2024/05/07 15:40:03 DEBUG : Using config file from "/home/amnesia/.rclone.conf"
2024/05/07 15:40:03 DEBUG : proton drive root link ID '': Has cached credentials
2024/05/07 15:40:04.618406 WARN RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401), Attempt 1
2024/05/07 15:40:04.618615 ERROR RESTY 401 GET https://mail.proton.me/api/core/v4/users: Invalid access token (Code=401, Status=401)
2024/05/07 15:40:04.747064 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422), Attempt 1
2024/05/07 15:40:04.747084 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422)
2024/05/07 15:40:04 DEBUG : Saving config "client_uid" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : Saving config "client_access_token" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : Saving config "client_refresh_token" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : Saving config "client_salted_key_pass" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : proton drive root link ID '': Cached credential doesn't work, clearing and using the fallback login method
2024/05/07 15:40:04 DEBUG : Saving config "client_uid" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : Saving config "client_access_token" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : Saving config "client_refresh_token" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : Saving config "client_salted_key_pass" in section "protonrc" of the config file
2024/05/07 15:40:04 DEBUG : proton drive root link ID '': couldn't initialize a new proton drive instance using cached credentials: failed to refresh auth: failed to refresh auth, de-auth: 422 POST https://mail.proton.me/api/auth/v4/refresh: Invalid refresh token (Code=10013, Status=422)
2024/05/07 15:40:04 DEBUG : proton drive root link ID '': Using username and password to log in
2024/05/07 15:40:06.319650 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4: Are you sure this is the correct domain? Please verify and try again. (Code=8002, Status=422), Attempt 1
2024/05/07 15:40:06.319671 ERROR RESTY 422 POST https://mail.proton.me/api/auth/v4: Are you sure this is the correct domain? Please verify and try again. (Code=8002, Status=422)
2024/05/07 15:40:06 Failed to create file system for "protonrc:": couldn't initialize a new proton drive instance: 422 POST https://mail.proton.me/api/auth/v4: Are you sure this is the correct domain? Please verify and try again. (Code=8002, Status=422)

welcome to the forum,

currently, proton support has a bunch of bugs and other issues.
there are many other open topics in the forum about that.
hopefully, one of those topics has a solution or workaround.

It is still in beta and maybe should be demoted to alpha:) unless you are golang developer willing to donate your skills and time to make it better I would not use it at the moment. Keep an eye on GitHub activity around it. Things can improve at some stage.

1 Like

Super weird, I didn't touch my configuration and now it works perfectly.

A temporary problem at proton?

Thanks in any case.

But from rclone you can't see the stored photos?
Does ProtonDrive store them elsewhere?

Could be proton hates rclone
https://www.reddit.com/r/rclone/s/18Eob5uRnA

rclone blocked by Proton Drive it seems

So i had rclone working with proton drive a month or two ago. Figured Iā€™d try it again.

It failed to connect and said the account was locked out. I went to the designated web page to request unlock and filled out the form.

Support replied as follows:

Hello,

Thank you for your message.

We have noticed that your login attempt to your account was blocked, due to your "Rclone" usage, and we have done this because it disrupts our network; we would advise you to stop using "Rclone" for cloud management, to avoid further interruptions. Kind regards,

Customer Support Proton Mail Abuse Team

NOTE: I submitted this same post to r/ProtonDrive and it's been waiting moderation for 8 hours or so. Not sure why. The Support team replied in about 10 minutes.

I doubt it has anything to do with rclone per se. But Proton Drive is only clear about how much their service cost (expensive). Everything else is secret:) So they can ban anybody they consider not suitable for their service. Pay and try if it is you or not.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.