Installation

Install Maxx Remote as a portable Desktop app or run it as a Docker server.
Tags:
Categories:

Goal / when to use

Get Maxx Remote running so you can open the UI and create or load a project.

  • Choose Desktop for commissioning laptops and day-to-day design work.
  • Choose Docker for an always-on server that browsers can reach on the network.

Prerequisites

  • Supported OS for Desktop, or a host that can run Docker
  • Network access to your amplifiers (see Prerequisites)
  • For automatic discovery (amplifiers and Dante TX sources): the host must receive the UDP broadcast / multicast traffic listed under Ports and discovery — on Docker that means host networking

Desktop application

  1. Download Maxx Remote from the Innosonix downloads page.
  2. Unpack or place the portable application where you want it — no installer is required.
  3. Start the application.
  4. On first launch, use Start a new project or import an existing project archive.

Expected result

The Maxx Remote window opens with the project splash / HOME UI. You can also reach the same UI in a browser at http://localhost:8000 while the Desktop app is running.

Server / Docker

Ports and discovery

Maxx Remote listens for more than the web UI. Automatic discovery uses UDP broadcast and multicast, which Docker’s default bridge network does not forward reliably when you only publish ports with -p.

TrafficAddress / portPurpose
TCP 8000host :8000Web UI and REST API
UDP 9453broadcast 255.255.255.255Innosonix amplifier discovery (INX / IDFM)
UDP 5353multicast 224.0.0.251mDNS — Dante device discovery (_netaudio-arc / _netaudio-cmc / _netaudio-dbc)
UDP 8702multicast 224.0.0.231Dante control-plane notifications (live TX updates)
UDP 8708multicast 224.0.0.233Dante heartbeats (device liveness)

Maxx Remote also sends outbound unicast UDP to Dante devices (ARC channel queries, typically ports 4440 / 4444 / 4455, and CMC registration, typically 8800). Those are device-side ports — they are not something you “publish” on the container; the host firewall must allow the outbound path.

Use host networking whenever you want automatic amplifier scan or Dante TX discovery:

docker run --detach --name maxx-remote --network host innosonix/maxx-remote:latest

Once the container is running, open:

http://<docker-host-ip>:8000

Alternative: published ports (UI only — no discovery)

If you only need the web UI and will add amplifiers by IP / hostname (and do not rely on Maxx Remote’s Dante discovery), bridge networking with a published HTTP port is fine:

docker run --detach \
  --name maxx-remote \
  -p 8000:8000 \
  innosonix/maxx-remote:latest

Compose equivalent:

services:
  maxx-remote:
    image: innosonix/maxx-remote:latest
    ports:
      - "8000:8000"
    # Discovery (INX + Dante) will not work reliably on the default bridge.
    # Prefer network_mode: host when you need ADD FROM NETWORK or Dante TX scan.

Do not expect a long -p 9453:9453/udp -p 5353:5353/udp … list to replace --network host for discovery. Map TCP 8000 for the UI; use host networking when discovery matters.

Option A — Export / import yourself

Use the UI Export / Import controls when you migrate to a new container.

Option B — Docker volume (preferred)

# create once
docker volume create maxx-remote-volume

docker run  --detach \
            --restart always \
            --name maxx-remote \
            --network host \
            --mount source=maxx-remote-volume,target=/root \
            innosonix/maxx-remote:latest

Expected result

Browsers on the network can open the Maxx Remote UI on port 8000, and projects survive container restarts when a volume is mounted. With --network host, ADD FROM NETWORK and Dante TX discovery can see devices on the same LAN segment.

Common mistakes