RetroAchievements login failed - Error 451
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
When RetroAchievements is enabled and the user/password is correct, it presents a weird error and the app can't login to RetroAchievements.
The error says "Error login failed - Error 451 - file unavailable for legal reasons"
This is happening in Retroarch Android.
As we have talked in the forum of RA (https://retroachievements.org/forums/topic/31974), perhaps this is as easy as change the login URL from "http" to "https".
And perhaps this is only happening in some countries. I'm testing from Spain.
HTTP Code 451 means some censored content. But perhaps this is fixed with a change from http to https.
Expected behavior
The login should work.
Steps to reproduce the bug
- From Retroarch Android, Configure and connect to RetroAchievements, with your username and password.
- Play some game.
Version/Commit
1.21.0
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Android 13
Affected Cores
No response
Environment information
No response
Relevant log output
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 from the RetroAchievements connection flow in RetroArch Android and reproduce the login failure on Android 13 with the credentials described. Check the login endpoint used by that flow, then verify that the expected behavior—successful authentication and gameplay access—works and is regression-tested; no source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- authentication, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100