[Bug] Launchbox scrapes or metadata aquisition not working

[stigzler]

RomM version
4.9.0-beta.3

Describe the bug
Scraping known good roms either solely or including launchbox results in no LB metadata found. Also,

when try to run Scheduled launcbox metadata update

To Reproduce
As above

Expected behavior
Launchbox metadata scrapes successfully.

Server (please complete the following information):

• OS: Ubuntu Server, docker

Client (please complete the following information):

• Device: Windows 11, chrome

Additional context
Possible relevant part of output:

Click here

```

romm | INFO: [RomM][nginx][2026-06-10 22:56:00] [redacted IP] | 192.168.50.1 | GET /rom/127 200 | 2195 | Unknown Unknown | 0.000
romm | DEBUG: [RomM][queue][2026-06-10 22:56:00] Getting jobs for queue low: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:00] Getting jobs for queue default: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:00] Getting jobs for queue high: 0 found.
romm | INFO: [RomM][httptools_impl][2026-06-10 22:56:00] 192.168.50.1:0 - "GET /api/tasks/status HTTP/1.0" 200
romm | INFO: [RomM][nginx][2026-06-10 22:56:00] [redacted IP] | 192.168.50.1 | GET /api/tasks/status 200 | 1072 | Chrome Windows | 0.048
romm | INFO: [RomM][httptools_impl][2026-06-10 22:56:02] 192.168.50.1:0 - "POST /api/tasks/run/update_launchbox_metadata HTTP/1.0" 400
romm | INFO: [RomM][nginx][2026-06-10 22:56:02] [redacted IP] | 192.168.50.1 | POST /api/tasks/run/update_launchbox_metadata 400 | 59 | Chrome Windows | 0.014
romm | INFO: [RomM][nginx][2026-06-10 22:56:04] [redacted IP] | 192.168.50.1 | GET /favicon-16x16.png 200 | 536 | Unknown Unknown | 0.000
romm | INFO: [RomM][nginx][2026-06-10 22:56:04] [redacted IP] | 192.168.50.1 | GET /favicon-32x32.png 200 | 1128 | Unknown Unknown | 0.000
romm | INFO: [RomM][nginx][2026-06-10 22:56:04] [redacted IP] | 192.168.50.1 | GET /favicon-16x16.png 200 | 536 | Unknown Unknown | 0.000
romm | INFO: [RomM][nginx][2026-06-10 22:56:04] [redacted IP] | 192.168.50.1 | GET /apple-touch-icon.png 200 | 5611 | Unknown Unknown | 0.000
romm | INFO: [RomM][nginx][2026-06-10 22:56:04] [redacted IP] | 192.168.50.1 | GET /favicon.ico 200 | 15406 | Unknown Unknown | 0.000
romm | DEBUG: [RomM][queue][2026-06-10 22:56:06] Getting jobs for queue low: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:06] Getting jobs for queue default: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:06] Getting jobs for queue high: 0 found.
romm | INFO: [RomM][httptools_impl][2026-06-10 22:56:06] 192.168.50.1:0 - "GET /api/tasks/status HTTP/1.0" 200
romm | INFO: [RomM][nginx][2026-06-10 22:56:06] [redacted IP] | 192.168.50.1 | GET /api/tasks/status 200 | 1067 | Chrome Windows | 0.110
romm | DEBUG: [RomM][queue][2026-06-10 22:56:11] Getting jobs for queue low: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:11] Getting jobs for queue default: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:11] Getting jobs for queue high: 0 found.
romm | INFO: [RomM][httptools_impl][2026-06-10 22:56:11] 192.168.50.1:0 - "GET /api/tasks/status HTTP/1.0" 200
romm | INFO: [RomM][nginx][2026-06-10 22:56:11] [redacted IP] | 192.168.50.1 | GET /api/tasks/status 200 | 1067 | Chrome Windows | 0.112
romm | DEBUG: [RomM][protocol][2026-06-10 22:56:12] % sending keepalive ping
romm | DEBUG: [RomM][protocol][2026-06-10 22:56:12] > PING b3 fa c4 4c [binary, 4 bytes]
romm | DEBUG: [RomM][protocol][2026-06-10 22:56:12] < PONG b3 fa c4 4c [binary, 4 bytes]
romm | DEBUG: [RomM][protocol][2026-06-10 22:56:12] % received keepalive pong
romm | DEBUG: [RomM][queue][2026-06-10 22:56:16] Getting jobs for queue low: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:16] Getting jobs for queue default: 0 found.
romm | DEBUG: [RomM][queue][2026-06-10 22:56:16] Getting jobs for queue high: 0 found.
romm | INFO: [RomM][httptools_impl][2026-06-10 22:56:16] 192.168.50.1:0 - "GET /api/tasks/status HTTP/1.0" 200
romm | INFO: [RomM][nginx][2026-06-10 22:56:16] [redacted IP] | 192.168.50.1 | GET /api/tasks/status 200 | 1067 | Chrome Windows | 0.110
romm | DEBUG: [RomM][protocol][2026-06-10 22:56:17] > TEXT '2' [1 byte]
romm | DEBUG: [RomM][protocol][2026-06-10 22:56:17] < TEXT '3' [1 byte]

</details>

[gantoine]

Post the container logs

[stigzler]

apols - attached:

rommLog.txt

[gantoine]

@stigzler do you have ENABLE_SCHEDULED_UPDATE_LAUNCHBOX_METADATA=true in your env vars?

[stigzler]

@gantoine - ah no for that log run (i turned it off on a debugging run and forgot to turn it back on). However - it's not that. Stopped server. set that to true and restarted server. Still getting the error. Attached new log with it set to true. 400 response from update_launchbox_metadata. New run log attached. My redacted compose.yml:

services:
  romm:
    image: rommapp/romm:latest
    container_name: romm
    restart: unless-stopped
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      # --- CORRECT DATABASE CONFIG ---
      - DB_HOST=[redacted]
      - DB_NAME=[redacted]
      - DB_USER=[redacted]
      - DB_PASSWD=[redacted] # Must be DB_PASSWD, not DB_PASS
      - ROMM_DB_DRIVER=mariadb
      # -------------------------------
      - ROMM_BASE_URL=https://[redacted].life
      - ROMM_AUTH_SECRET_KEY=[redacted]
      - SCREENSCRAPER_USER=[redacted]
      - SCREENSCRAPER_PASSWORD=[redacted]
      - IGDB_CLIENT_ID=[redacted]
      - IGDB_CLIENT_SECRET=[redacted]
      - RETROACHIEVEMENTS_USER=[redacted]
      - RETROACHIEVEMENTS_API_KEY=[redacted]
      - HASHEOUS_API_ENABLED=true
      - LAUNCHBOX_API_ENABLED=true
      - ENABLE_SCHEDULE_UPDATE_LAUNCHBOX_METADATA=true
      - HLTB_API_ENABLED=true
      - HLTB_API_KEY=dummy-not-needed
      - LOGLEVEL=DEBUG
    volumes:
      - /home/[redacted]/appdata/romm/config:/romm/config
      - /mnt/pool/Media/Games/media-sets/romm:/romm/resources
      - /mnt/pool/Media/Games:/romm/library
    ports:
      - 8282:8080
    networks:
      - media_net
    depends_on:
      romm-db:
        condition: service_healthy
  romm-db:
    image: mariadb:latest
    container_name: romm-db
    restart: unless-stopped
    environment:
      - MARIADB_ROOT_PASSWORD=[redacted]
      - MARIADB_DATABASE=[redacted]
      - MARIADB_USER=[redacted]
      - MARIADB_PASSWORD=[redacted]
    volumes:
      - /home/[redacted]/appdata/romm/mysql:/var/lib/mysql
    networks:
      - media_net
    healthcheck:
      test:
        - CMD
        - healthcheck.sh
        - --connect
        - --innodb_initialized
      interval: 10s
      timeout: 5s
      retries: 3
networks:
  media_net:
    external: true

mapped to port 8282 because 8080 already taken

Dunno if this is related in any way, but I'm also getting "API key invalid" on Hasheous

Access through nginx reverse proxy. Settings:
Block Copmmon Exploits: true
WebSockets Support: true
Force SSL: true
https/2 support: true
cache assets: false

rommLbProblem.log

[gantoine]

Ah it's likely your server can't reach hasheous, and possibly launchbox gamesdb. Exec into the container and see if you can manually react those websites: https://hasheous.org/api/v1 and https://gamesdb.launchbox-app.com

[stigzler]

romm.log

Hmmm. Most odd. I did that and you guessed right. Not reaching either. However it IS reaching screenscraper, igdb and retroacievments.

Some ai'ing later, i could make it reach them by:

apk update
apk add ca-certificates
update-ca-certificates

Which gives:

/romm # curl -I -4 https://hasheous.org/api/v1
HTTP/2 404
date: Sat, 13 Jun 2026 21:04:41 GMT
alt-svc: h3=":443"; ma=86400
server: cloudflare
via: 1.1 Caddy
x-correlation-id: 59d274d4-f6a9-414a-abed-289e4c84e9ca
cf-cache-status: DYNAMIC
strict-transport-security: max-age=15552000; includeSubDomains; preload
x-content-type-options: nosniff
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=5sWzHr2bT%2F%2BA%2Ftn%2BN7MOmScmGEkxvewLqGI%2FDfM%2ByJtrAAVz7m3OHI8qAOKF15FZkC%2FgqegSZ14aJaTOC%2FcenyL%2F6rYCldasmoXUeZhtXj09UPCdE%2FnNvQnTMPlr%2Fgk%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a0b40c92fdd447cf-LHR

/romm # curl -I https://gamesdb.launchbox-app.com
HTTP/2 405
allow: GET
alt-svc: h3=":443"; ma=2592000
content-type: text/html; charset=utf-8
date: Sat, 13 Jun 2026 21:04:46 GMT
server: Kestrel
strict-transport-security: max-age=2592000

However, errors still persist in ui. If i restart the container, then I go back to not being able to connect to those two servers again from within the container. Running the update command fixes these again, but still errors out in the UI.

God I hate networking.

[stigzler]

@gantoine just for clarity - am I guessing right that that PR isn't fixing this issue, rather it allow the update_launchbox_metadata request to run when LAUNCHBOX_API_ENABLED is enabled not when ENABLE_SCHEDULED_UPDATE_LAUNCHBOX_METADATA is so? If so, I'm not sure this fixes my issue, but guessing you may have known this and just fixing a side issue?

As it stands, I still cant access hasheous or launchbox😔 Given I'm developing a launchbox plugin, that's a bit of an issue!

[gantoine]

For launchbox, try CURL-ing curl -I https://gamesdb.launchbox-app.com/Metadata.zip instead, it's the direct link to the download. You'll also need to set ENABLE_SCHEDULED_UPDATE_LAUNCHBOX_METADATA=1 to download the game DB locally.

[stigzler]

Set it to 1 instead of true. No dice. Same errors despite being available.

➜ ~ docker exec -it romm /bin/sh
/romm # curl -I https://gamesdb.launchbox-app.com/Metadata.zip
HTTP/2 200
accept-ranges: bytes
alt-svc: h3=":443"; ma=2592000
content-type: application/x-zip-compressed
date: Sun, 14 Jun 2026 12:48:27 GMT
etag: "1dcfbd3e10ec983"
last-modified: Sun, 14 Jun 2026 08:00:45 GMT
server: Kestrel
strict-transport-security: max-age=2592000
content-length: 104561923

both inside and outside the container.

If relevant, lb shows as available in the ui:

😵‍💫

[stigzler]

Still stuck on this. I did some network maintenance and cured the hasheous issue through changing the TCP and checksum offloading (apparently - AI solved it - waaay beyond my networking knowledge this):

sudo sysctl -w net.ipv4.tcp_rmem="4096 87380 4194304"
sudo sysctl -w net.ipv4.tcp_wmem="4096 16384 4194304"
sudo ethtool -K eno1 tx off rx off

Restarted server. Restarted service.
however, the launchbox metadata update is still erroring. out.

the site is contactable in and out of the container:

➜  ~ curl -I https://gamesdb.launchbox-app.com/Metadata.zip
HTTP/2 200
accept-ranges: bytes
alt-svc: h3=":443"; ma=2592000
content-type: application/x-zip-compressed
date: Tue, 16 Jun 2026 12:52:41 GMT
etag: "1dcfd663b063035"
last-modified: Tue, 16 Jun 2026 08:00:47 GMT
server: Kestrel
strict-transport-security: max-age=2592000
content-length: 104616373

➜  ~ docker exec -it romm /bin/sh
/romm # curl -I https://gamesdb.launchbox-app.com/Metadata.zip
HTTP/2 200
accept-ranges: bytes
alt-svc: h3=":443"; ma=2592000
content-type: application/x-zip-compressed
date: Tue, 16 Jun 2026 12:56:30 GMT
etag: "1dcfd663b063035"
last-modified: Tue, 16 Jun 2026 08:00:47 GMT
server: Kestrel
strict-transport-security: max-age=2592000
content-length: 104616373

No idea whether this is my network or romm!?? Everything else on romm working flawlessly.

[stigzler]

Not sure what info you guys need, but attached an abridged log showing different launchbox operation failiurs (decryption of scenario in comment in log). Again can curl the address both in and out of container.

RommLaunchboxBugs.log