Quickstart

Run the container

services:
  webstation:
    image: lscr.io/linuxserver/webstation:romm
    container_name: webstation
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - SUBFOLDER=/streaming/
      - BROKER_SECRET=change-me
    volumes:
      - /path/to/config:/config
      - /path/to/library:/romm/library
    ports:
      - 3000:3000
      - 3001:3001
    shm_size: "1gb"
    restart: unless-stopped

You also need a GPU passed through, or most emulators won't run: /dev/dri for Intel or AMD, or the NVIDIA container runtime with driver 595.80 or newer for NVIDIA, plus the /dev/nvidia-modeset device specifically, which is easy to miss since the container toolkit doesn't add it automatically. See Running the container for the full recipes.

Wire it into RomM

Add a streaming container entry to RomM's config.yml:

streaming:
  containers:
    - platform: ps2
      host: /streaming
      broker_host: http://10.0.1.56:3000
      subfolder: /streaming
      broker_secret: "change-me"
      protocol: webstation
      emulator: pcsx2
      label: WEBSTATION

Two things trip people up here.

The library mount on this container has to use the same host folder and the same /romm/library path as the one on your RomM container. RomM sends ROM paths as it sees them, so a different mount fails every launch with a 404 reading rom not found at <path>. If you can't match it, see Mounting the library somewhere else.

broker_secret here and BROKER_SECRET on the container also have to be the exact same string. A mismatch fails every activate, join, and exit call with a 403 and a broker log line reading rejected request: bad or missing broker secret. This already has a full writeup, so see Reverse proxy troubleshooting rather than repeating it here.

See Wiring it into RomM for what every field in this block actually does.

Set up each emulator once

This is the step most first launches fail on. A single-game launch reuses whatever configuration the emulator already has on disk. It doesn't set anything up for you, so before RomM can boot a game straight into an emulator, you need to open that emulator from the desktop once and get it working by hand: BIOS or firmware installed, keys in place, controller responding. Launch a desktop session from RomM (or open https://yourhost:3001/streaming/ directly) to get there.

Emulator setup has the full walkthrough per emulator. A few of the sharper pitfalls, so you're not caught flat-footed:

• Eden won't run anything until you install prod keys and firmware yourself, from its Tools menu.
• Cemu needs a keys.txt uploaded by hand, and is genuinely finicky. Expect to launch it more than once before controller and audio settings stick.
• Xemu needs three specific files uploaded through its own startup menu (the MCPX boot ROM, the flash ROM, and a hard disk drive image), and has to be relaunched once after that before it will boot anything.
• Xenia needs a profile created from the desktop first: accept the "No Profiles Found" prompt once. Skip this and a single-game launch stalls forever behind that same prompt with nothing to click it.
• shadPS4 needs a version downloaded through its own version manager before it can run anything at all.

There's no shortcut past this. A real game with a real controller is the only way to confirm an emulator's setup is actually done.

Put it behind a reverse proxy (recommended)

Most real deployments want this: serving the container from a subfolder of RomM's own origin, rather than as a separate address, is what makes the room's camera, microphone, and pointer tracking work at all.

SUBFOLDER has to equal the proxy's mount path exactly, trailing slash included, or nothing lines up. And most proxies strip that path prefix by default, which breaks every asset with a 404. See Reverse proxy for the full contract and per-proxy recipes (nginx, Nginx Proxy Manager, Caddy, Traefik).

Launch a game

Start a game from RomM the way you normally would. It opens the room right in your browser, with the emulator already running inside it. See Using the room for what the controls do: chat, webcam, handing a controller to someone else, ending the session.