Retroarch has no ssl support

General
1

Hi there,

Retroachievements is not working for me on pixie patch 2 on rg35xx sp. I have tried my best to find the issue.

It looks a lot like retroarch on my device was compiled without ssl functionality. Would that be possible? And if so, can you help me with the compile command/flags you use to (cross)compile retroarch, so I can try to compile it with ssl support?

Thank you!

2

It should have been compiled with SSL support. Far as I know we always have.

It’s more likely you have some other issue, not properly connected to the network, incorrect time/date, etc.

muOS_20250623_2017_0
muOS_20250623_2017_0720×720 37.4 KB

2 Likes
3

I don’t think it is ssl support, I’m facing the same problem but with a rg35xxh, i guess that the issue is that muos pixie has retroarch version 1.20 and the latest version of retroarch is 1.21. i have tested at my pc that was at version 1.19 (also with RA not connecting) after updating to 1.21 it logged and connected fine. As muos is custom pre configured i don’t know if it is possible to update only retroarch.

4

Thanks for the report, but to remove any cloud of doubt this is not a muOS issue.

muOS Pixie has been out for several months now, and RetroAchievements is working reliably for a wide range of users on multiple devices, including the RG35XX-H. If there were a systemic problem with RetroArch integration or its version in muOS, we would have had numerous widespread reports and confirmations by now. However, this has not been the case.

Your issue sounds localised, and the fact that it worked after updating to 1.21 on your PC does not necessarily mean the problem is due to the version difference on muOS. RetroAchievements continues to function correctly on 1.20 for other users.

That said, here are a few things you can check:

  • Verify your RetroAchievements credentials. A typo in username or password will silently fail afaik.
  • Check your device date, time, and timezone settings. If your clock is off (especially in the past or future), SSL/TLS connections may be rejected.
  • Ensure you have a stable network connection. DNS issues can sometimes interfere silently.
  • As a last resort, reflash your mSD card with a clean Pixie image to eliminate any file corruption or misconfiguration.

At this time, muOS does not support individual updates to RetroArch outside of our tested and configured releases, due to how tightly integrated it is with system modules and internal scripting. We do not apply any custom patches with RetroArch and we always ensure features like RetroAchievements function correctly.

For now, rest assured that RetroAchievements works just fine under 1.20 on muOS Pixie, and your issue is likely local or configuration related. Hope this helps. Let us know how you go after checking those things.

2 Likes
5

I have tested these things thoroughly.

My Dns server receives the requests and send the ip addresses back correctly

Time looks to be fine. It is setup with ntp and appears to be working correctly

The credentials are correct. Tripple checked it and the same credentials log me in on the steam deck just fine.

  1. I have reflashed and have the same issue.

That being said, I just confirmed that retroarch indeed has ssl support listed as ‘yes’. I feel kinda stuck as it appears to be working for most people, just not for me and a few others.

EDIT: I managed to get it working by using my phone’s hotspot. So it seems the problem is something in my network that it doesn’t like. My guess is it is maybe related to my adblocking and retroachievements’ cloudflare protection.

1 Like
6

Yes, it is indeed a network connection problem, not muos pixie nor retroarch 1.20 version, i have tested with network hotspot and it is working properly!