You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 2, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 2, 2026. It is now read-only.
2026/05/06 16:56:32 request failed: POST https://mail.proton.me/api/auth: [9001] 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
2026/05/06 16:56:32 [9001] 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
hydroxide$ ./hydroxide auth x@proton.me
Password:
2026/05/08 11:06:30 request failed: POST https://mail.proton.me/api/auth: [9001] 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
2026/05/08 11:06:30 [9001] 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
hydroxide$
I am also running into this issue with hydroxide. However, I've had luck with the ferroxide fork. Since it's a fork, I'm fairly certain you can just use the same auth file for hydroxide afterwards too.
I am also running into this issue with hydroxide. However, I've had luck with the ferroxide fork. Since it's a fork, I'm fairly certain you can just use the same auth file for hydroxide afterwards too.
Activity
nxjoseph commentedon May 6, 2026
Same here...
xb0s0n commentedon May 8, 2026
Same here:
hydroxide$ ./hydroxide auth x@proton.me
Password:
2026/05/08 11:06:30 request failed: POST https://mail.proton.me/api/auth: [9001] 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
2026/05/08 11:06:30 [9001] 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
hydroxide$
nxjoseph commentedon May 11, 2026
Unfortunately, this problem still exist in the new version v0.2.32
@emersion
mail/hydroxide: Update 0.2.31 => 0.2.32
fisheyes commentedon Jun 22, 2026
Is there any know workarounds with this? Or is this game over?
74k1 commentedon Jun 22, 2026
I am also running into this issue with hydroxide. However, I've had luck with the ferroxide fork. Since it's a fork, I'm fairly certain you can just use the same auth file for hydroxide afterwards too.
fisheyes commentedon Jun 22, 2026
Thanks so much... Back up and running.
mail/hydroxide: Update 0.2.31 => 0.2.32
mail/hydroxide: Update 0.2.31 => 0.2.32
fix(protonmail): bump `defaultAppVersion` to solve CAPTCHA
fix(protonmail): bump `defaultAppVersion` to solve CAPTCHA
fix(protonmail): bump `defaultAppVersion` to solve CAPTCHA