Skip to content
This repository was archived by the owner on Aug 2, 2026. It is now read-only.
This repository was archived by the owner on Aug 2, 2026. It is now read-only.

CAPTCHA #328

Open
Open

Description

@donaldtrump2049

2026/03/25 15:31:38 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/03/25 15:31:38 [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

Activity

  1. nxjoseph commented on May 6, 2026

    @nxjoseph

    Same here...

    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
    
  2. xb0s0n commented on May 8, 2026

    @xb0s0n

    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$

  3. nxjoseph commented on May 11, 2026

    @nxjoseph

    Unfortunately, this problem still exist in the new version v0.2.32

    @emersion

  4. fisheyes commented on Jun 22, 2026

    @fisheyes

    Is there any know workarounds with this? Or is this game over?

  5. 74k1 commented on Jun 22, 2026

    @74k1

    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.

  6. fisheyes commented on Jun 22, 2026

    @fisheyes

    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.

    Thanks so much... Back up and running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions