Steam Deck: "Could not communicate with https://retroachievements.org"

RetroArch Linux devices
#1

Hi! I’ve been enjoying using RetroAchievements through RetroArch on my Steam Deck, but about a month or two ago I started getting a “Could not communicate with https://retroachievements.org” error whenever I launch a game through RetroArch. The error happens on any emulator I’ve tried that’s running through RetroArch. I apologise if this is more a RetroAchievements issue rather than a RetroArch one, I haven’t been able to find definitively where the error is coming from.

I’ve tried updating and reinstalling RetroArch, resetting my token, changing my password, and deleting (alternately) the “cheevos_token” or “cheevos_password” fields in retroarch.cfg. My Steam Deck is connected to the internet and not behind any kind of firewall. RetroArch itself can otherwise connect to the internet with no problem, being able to update cores etc. The problem occurs in both the RetroArch app through the Steam store and the standalone version that was installed through EmuDeck, though neither had any issue connecting previously. Other apps like DuckStation can connect to RetroAchievments without any problem.

I enabled logging and get this (for example, using Akumajou Special which does seem to match the hash that is initially generated):

[INFO] [RCHEEVOS]: Load started, hardcore active [INFO] [RCHEEVOS]: Using host: https://retroachievements.org [INFO] [RCHEEVOS]: Found 1 potential consoles for nes file extension [INFO] [RCHEEVOS]: Trying console 7 [INFO] [RCHEEVOS]: Ignoring NES header [INFO] [RCHEEVOS]: Hashing 262144 byte buffer [INFO] [RCHEEVOS]: Generated hash 96084e640ed9a02c644b39986c269662 [INFO] [RCHEEVOS]: Attempting to login Protosimian (with password)

…

[ERROR] [RCHEEVOS]: Error resolving hash 0: Internal error. (automatic retry in 250ms) [ERROR] [RCHEEVOS]: Error logging in 0: Internal error. (automatic retry in 250ms) [ERROR] [RCHEEVOS]: Error resolving hash 0: Internal error. (automatic retry in 500ms) [ERROR] [RCHEEVOS]: Error logging in 0: Internal error. (automatic retry in 500ms) [ERROR] [RCHEEVOS]: Error resolving hash 0: Internal error. (automatic retry in 1000ms) [ERROR] [RCHEEVOS]: Error logging in 0: Internal error. (automatic retry in 1000ms) [INFO] [RCHEEVOS]: Could not communicate with https://retroachievements.org [INFO] [RCHEEVOS]: Error logging in: Load aborted

My RetroAchievments account is otherwise acting normally - I can connect through RetroArch on my PC using the same username/password/token (before and after changing it). I also made a second RetroAchievments account but the same issue happens - I can connect when using my PC but not on my Steam Deck.

Has anyone else had this issue or perhaps have any other suggestions as what I could do to fix it? Again, apologies if this is the wrong place to ask! Thanks!

#2

An interesting update, one of the users on the RetroAchievements forums found that connecting to the internet via a mobile hotspot rather than their regular wifi resulted in RetroArch being able to connect to RetroAchievements.

I’ve tested this and I have the same results: RetroArch through my Steam Deck cannot connect to RetroAchievements when using my regular wifi. RetroArch through my PC, using the same wifi, can connect. RetroArch through my Steam Deck can connect to RetroAchievements when using my mobile hotspot.

I suspect there may be some issue with the type of network settings or router I’m using in combination with a Steam Deck?

#3

I think you also get a “can’t connect” message if there are no achievements for that console. For instance, I don’t think Gamecube has any achievements yet. Which core are you loading? Maybe there just are no achievements for that core?

Compatible Emulators list: https://docs.retroachievements.org/Emulator-Support-and-Issues/

#4

Or maybe this link is better? I was trying to find an “official” list.

#5

Hi! I was finally able to find the issue and fix it, thanks to help from the users on the RetroAchievements forums.

The problem seems to be that RetroArch has issues connecting through networks that use the IPv6 protocol. By changing the connection settings for your network through the Steam Deck’s desktop mode to disable IPv6, it seems the issue is resolved for most people. In my case I also had to make a few changes on my own network before it started working for me.

I hope that helps anyone who might be having the same problem!