Session info wipe unnecessarily cuts connection to Proton Drive (error 422)

I have found

client_uid =
client_access_token =
client_refresh_token =
client_salted_key_pass =

in my rclone config after a failed login attempt, caused by a connection timeout.

I assume this is done to rule out the session as the culprit, however it does not work well with Proton.

1. If a user has 2FA enabled, wiping the session info means 2FA is required again. Manual intervention is required at this point.
2. It seems that logins through a VPN (surprisingly even ProtonVPN) get blocked by Proton Sentinel. I am not sure why exactly, because it works for their Android apps and in a browser, but with Rclone it does not. This means VPN users have to completely disable it, before they are able to log in again.

In sum, I think something needs to be done regarding these session info wipes. It seriously negatively impacts the user experience of anyone using 2FA (which should be anyone :P), even more so if you use any VPN.

Originally posted by @LivingUserError in https://github.com/rclone/rclone/issues/7864#issuecomment-2413847848

Version info:

rclone v1.68.0
- os/version: endeavouros (64 bit)
- os/kernel: 6.11.3-arch1-1 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.23.1
- go/linking: dynamic
- go/tags: none

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.