ProtonMail / ProtonMail/WebClients
Local dev: 422 error on login (potentially abusive traffic)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
We are happy to answer your questions about the code or discuss technical ideas.
Please complete the following checklist (by adding [x]):
- [ x ] I have searched open and closed issues for duplicates
- [ x ] This isn't a feature request
- [ x ] This is not a report about my app not working as expected
Hi there,
Trying to run the project locally to contribute to the project, but unfortunately I can not get past the login screen. Using yarn version 4.5.3, node 20.14.0.
Ran yarn workspace proton-calendar start, and then entered Proton account details at localhost:8080/login screen. I'm receiving 200 for /api/core/v4/auth/info, but 422 Unprocessable Content for /api/core/v4/auth:
{
"Code": 2028,
"Error": "We are detecting potentially abusive traffic coming from your network and have temporarily blocked logins. If you believe this is in error, please contact us here: https://proton.me/support/appeal-abuse",
"Details": {}
}
Proxy seems by default to redirect /api,/internal-api -> https://mail.proton.me.
I noticed #419, #343 and #304 also describe issues with getting a local dev environment running, but I'm not seeing any references to this specific problem. (I'm not getting any captchas, for instance).
Also tried re-connecting to other VPN servers, but that did not seem to resolve the issue. Any help would be greatly appreciated!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the local command yarn workspace proton-calendar start and reproduce the login request from localhost:8080/login. Inspect the proxy behavior for /api and /internal-api, along with responses from /api/core/v4/auth/info and /api/core/v4/auth; done means the local development login flow no longer returns the reported 422 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100