RomM App For Cloudron
-
There is no metadata by default, so yes, it has to reach out somewhere unless you want to type out your own metadata into the editor. It should by default have hasheous, but I haven't always had tons of success with it's proxy.
Sorry about the dev api error. screenscraper isn't usable right now without me applying for a dev key.(screenscraper needs a dev key and user auth) Romm used to ship their key in the code, but removed it recently.
On my own server, I've set up IGDB for now. -
There is no metadata by default, so yes, it has to reach out somewhere unless you want to type out your own metadata into the editor. It should by default have hasheous, but I haven't always had tons of success with it's proxy.
Sorry about the dev api error. screenscraper isn't usable right now without me applying for a dev key.(screenscraper needs a dev key and user auth) Romm used to ship their key in the code, but removed it recently.
On my own server, I've set up IGDB for now. -
There is no metadata by default, so yes, it has to reach out somewhere unless you want to type out your own metadata into the editor. It should by default have hasheous, but I haven't always had tons of success with it's proxy.
Sorry about the dev api error. screenscraper isn't usable right now without me applying for a dev key.(screenscraper needs a dev key and user auth) Romm used to ship their key in the code, but removed it recently.
On my own server, I've set up IGDB for now.@eyecreate I started over and added the IGDB info and restarted the app then proceeded with the initial account creation. IGDB's connection is valid. I uploaded a new set of NES roms that I got from Vimmdotnet (in case it was a rom issue). Ran a scan and I still don't see them. They are being detected though. What am I doing wrong?
Edit: I downloaded the NES roms from the romM demo site to make sure it's not a rom issue so it must be a scan issue. I keep getting this error when manually triggering one regardless of which method I try (quick, complete, etc)
Scan failed: Quick Scan is already queued -
Started over again. This time I uploaded the roms and set IGDB info before setting up the account/app. I triggered a quick scan and in another tab I watched the log. The scan is definitely getting stuck. I triggered a new scan attempt in another tab and you can see the failed messages.
-
On RomM's discord, I found some clues related to quick scan getting stuck:
Clue 1
reverse proxy setup that enable Web sockets is onClue 2
This is for proxmox but might be related?
`There is a new worker just for scans and the update script doesn't create the new service, or seem to update the ones that are there. The updates are in the script to make a new romm lxc though.` https://github.com/community-scripts/ProxmoxVE/blob/main/install/romm-install.sh (starts at line 353)Clue 3
disable launchboxIf it's a typo and they meant lunchbox, I can definitely help with that.
Another user reported having scan issues in 5.3.1, but not in 5.2.0. I joined late to the party so I don't have a 5.2.0 backup to revert to to confirm.
-
-
-
-
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login