Captcha error when using Proton Drive

Hi! I'm trying to set up Rclone for the first time and would like to use ProtonDrive as my remote. I'm on a Linux server.

I've followed the guide but whenever I try a command that uses the remote, I get this error:
2024/09/21 14:35:18.138202 WARN RESTY 422 POST https://mail.proton.me/api/auth/v4: For security reasons, please complete CAPTCHA. If you can't pass it, please try updating your app or contact us here: https://proton.me/support/appeal-abuse (Code=9001, Status=422), Attempt 1

If it's useful context, I have 2FA enabled. I don't think it's a usage restriction as I got the error right from the first try.

I'm not sure I understand this part of the guide in my case, so this might be related:

NOTE: The Proton Drive encryption keys need to have been already generated after a regular login via the browser, otherwise attempting to use the credentials in rclone will fail.

Anything I can do about it? Should I contact Proton? Thank you :pray:

welcome to the forum

i would try to login to proton website, see if that works.
if that works, then try rclone again.

if any of that does not work, contact proton.
let us know their reply...

Thanks for the reply :slight_smile:

Do you mean connecting to their site from the server through SSH? Because it works perfectly when I try to log in from my regular computer.

I've already contacted Proton and will let you know!

login to their website - https://proton.me

sorry, not understanding your setup?

what server? where are you running rclone? on that server, on that regular computer?
are the server and the computer using the same public ip address?

have you tried to run rclone on the regular computer?

I have a VPS Linux server where Rclone is installed and on which I'm trying to configure Proton Drive.

Then there's my regular computer from which I can log in to Proton Drive with no issue (through the browser). They're not the same machine so different IP, but I haven't tried running Rclone and connecting to Proton drive from it!

is your instance running inside a virtual machine, with its own dedicated ip address, and root access?
or
just another login user running on the shared server, all sharing the same public ip address?

what is the company?

It's a Hostinger VPS (KVM 1). If I understand things correctly, I think it has its dedicated IP address.

Five days later, I have finally head back from Proton...

So maybe you ask them to create and document open API - then 3rd party tools like rclone can use it to its full potential.

At the moment rclone is using some reverse engineered way somebody was so patient and kind that included in rclone. It is one man project and if this person is busy or lost interest nothing better can be done - until somebody else will be willing to work on this.

Yeah I see. I asked them about the API, I'll share their response if it's any interesting. I've had Proton Drive for two years and have basically been unable to use it because of its lack of features, it's a real shame :frowning:

You are not the only one. I think following their secure email success they are trying to up-sale other services. Unfortunately both VPN and storage are really inferior compared to competition. Nothing justifies their premium price. Their storage is 100%+ more expensive than other better market offerings and its usage is effectively limited only to other Proton products.

People can only push them by cancelling their contracts stating exact reasons.

They're trying to launch too much stuff at once, so everything is half baked. I think in a few years if they keep on developing their services it'll be great, but for now you're right, it's overpriced.

I've thought of cancelling my subscription but now that I've got all my emails on it, it'd be a pain. I think their VPN is really good though (on iOS at least), I've had no problem with it, but Proton Pass has been a huge disappointment as well.

It's not looking good:

As for the topic of providing a public API, it's a bit complex due to the end-to-end encryption we employ. Offering an API involves challenges that go beyond those faced by more conventional services. Specifically, maintaining our high standards for security and encryption while providing public access requires careful consideration.

We are looking closely at every suggestion our customers are reporting and try to implement it in future updates to make Proton Drive more user-friendly.

For future reference, you can also create a feature request on UserVoice by visiting the following link:
Proton Drive: Hot (725 ideas) – The Voice of the Proton Community