Jump to content
LaunchBox Community Forums

Recommended Posts

Posted

Hi!! Until yesterday, RA achievements had been working without problems in LB, but suddenly it stopped working. Checking the options, I discovered that the Retroachievements API was incorrect. I filled out all the information again (username, password, and API key), but it still shows that the API is incorrect. I also tried changing it in RA, but the new one still gives the same error.

Any idea what could be causing the error?

image.thumb.png.28efec233bfac8fa8155166b697adea8.png

Posted (edited)

Same here. Same behaviour in the 'options' window since the recent manteinance. I even have reset my API Key to no avail. The API Key itself works fine with all the endpoints I've tried so far, including the GetUserSummary endpoint that Launchbox log shows as the one being used to check the credentials. Also, achievements are working fine in each emulator I've tested so far.

The command: curl -s "https://retroachievements.org/API/API_GetUserSummary.php?u=[redacted]&y=[redacted]" with my login and key works fine:

Quote

{"User":"[redacted]","MemberSince":"[redacted]","LastActivity":{"ID":0,"timestamp":null,"lastupdate":null,"activitytype":null.... 

Queries to this endpoint with different 'g' and 'a' parameters to the default seem to work fine as well.

The same command with a wrong Login or Key gives:

Quote

{"message":"Unauthenticated.","errors":[{"status":419,"code":"unauthorized","title":"Unauthenticated."}]}

It looks like everything works just fine. Tested several other endpoints and they seem to work.

Launchbox log gives:

Quote

PM EXCEPTION IGNORED: The remote server returned an error: (451) unused. at System.Net.HttpWebRequest.GetResponse() at Unbroken.LaunchBox.Windows.RetroAchievements.RetroAchievementsApi.GetUserSummary(String username, String apiKey, String summaryUser, Int32 recentGamesCount, Int32 recentAchievementCount)

Which is strange. Might be the case of Launchbox User-Agent query being rejected but I cannot check since I don't know which User-Agent is actually using.

Perhaps you could enable debug logs and check the same exception occurs and results in the same 451 error?

 

TL-DR: Launchbox shows the key as invalid in the options window even with a correct, functional  and tested key. This error happens since the last RA manteinance.

Achievements work fine for me in emulators for the time being, the only place they just don't work is the "achievements profile" of the Launchbox UI, where you can check the points, games recently played and such. Since this element is not working, is not showing on the top bar where retroachievemnts points are usually shown. Also "Failed to grab achievement information!" message in the "View achievements profile..." option in the menu. This worked fine prior the recent RA servers maintenance

 

Thanks in advance

Edited by BourbaKiND
Posted (edited)

Still giving me the error in LB 😔

I've found that

Quote

curl -s "http://retroachievements.org/API/API_GetUserSummary.php?u=[redacted]&y=[redacted]" with my login and key

(ie. using http and NOT https) does indeed give me:

Quote
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"><html> <head> <title id="1"> Error 451 </title> </head> <body> <CENTER> <h1> HTTP 451 – File unavailable For Legal Reasons </h1> </CENTER> </body></html>
* shutting down connection #0

which is what LB logs shows. If I type https, it works as described yesterday. I guess LB is using http and not https. Could anyone test both commands with their credentials and check the behavoiur of RA in their end, please?

I don't know if they changed something since last manteinance or it's something wrong in my connection (proxies, etc) ??

Thank you in advance

Edited by BourbaKiND
Posted
On 8/17/2025 at 12:46 PM, MrDeKat said:

My Retroachievements API is back up and running in LB!!

Despite what I had said, on Sunday night (Spanish time) I got the same error again.

Posted

We've talked with the RetroAchievements team. A major ISP in Spain is currently blocking HTTP traffic to their API. Currently it sounds that HTTPS is still working so I'll take a look at the code and get it all converted before our next release. In the meantime the only work around I'm aware of is to use a VPN.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...