-
-
Notifications
You must be signed in to change notification settings - Fork 14
Troubleshooting
abduznik edited this page Apr 6, 2026
·
2 revisions
- Check that your RomM server is running and reachable
- Verify the URL includes the correct port (e.g. http://192.168.1.100:8285)
- If using Tailscale, make sure both devices are on the same tailnet
- Try accessing the RomM web UI from a browser on the same device first
- If using HTTPS, check your certificate is valid
- Freegosy silently re-authenticates using stored credentials
- If this keeps happening, switch to API Key auth (more stable)
- Go to RomM Settings → Client API Tokens → Generate new token → paste into Freegosy Settings
- Download the emulator from Settings → Emulators
- If already installed, the executable may have been moved or renamed
- On macOS, ensure the .app bundle is in the Freegosy emulators directory (not Applications)
- The error message shows the exact core filename and expected path
- Freegosy will attempt to download the core automatically on the next launch attempt
- You can manually place the core .dll (Windows) or .dylib (macOS) in {retroarch}/cores/
- Launch the game at least once in the emulator to create the save directory
- Then retry the sync
- This appears when Freegosy cannot automatically determine the Title ID / save folder
- A folder picker dialog will appear showing available save folders
- Select the correct one — Freegosy will remember it for future syncs
- For Eden: folders are named as 16-character hex Title IDs (e.g. 0100704000B3A000)
- For Azahar: folders are in the sdmc directory
- Usually means missing Visual C++ redistributables or DirectX
- Install the latest VC++ redist from Microsoft
- Install DirectX End-User Runtime
- Run in Terminal: xattr -rd com.apple.quarantine /path/to/Freegosy.app
- Or right-click the app → Open → Open anyway
- Known RomM server-side bug in 4.8.0 where PUT /api/roms/{id}/props returns 200 but doesn't persist
- Workaround: update RomM to a newer version if available, or wait for upstream fix
- Freegosy correctly sends the request; the issue is server-side