AltMount (Core Service)¶

AltMount is a Usenet-backed WebDAV and streaming service. It accepts NZBs from Arr applications through a SABnzbd-compatible API, reads content from one or more NNTP providers, and makes that content available through WebDAV, a built-in FUSE or rclone mount, symlinks, or STRM files.

In DUMB, AltMount is a core Usenet workflow service. DUMB installs and starts AltMount, supplies its baseline configuration, embeds its UI, and connects enabled Sonarr, Radarr, Lidarr, and Whisparr instances whose core_service includes altmount.

Workflow diagram¶

%%{ init: { "flowchart": { "curve": "basis" } } }%%
flowchart TD
    A([Request Sources:<br/>Seerr, Trakt,<br/>Plex Watchlist,<br/>NeutArr])
    B[Arr Services:<br/>Sonarr, Radarr,<br/>Lidarr, Whisparr]
    C[[Prowlarr / Usenet Indexers]]
    D[AltMount<br/>SABnzbd-compatible API]
    E@{shape: cloud, label: "NNTP Providers"}
    F[[Content Access:<br/>WebDAV + selected<br/>mount mode]]
    G[Import Strategy:<br/>NONE / SYMLINK / STRM]
    H[Arr Import +<br/>Library Organization]
    I([Media Servers:<br/>Plex, Jellyfin, Emby])
    J[DUMB Setup + Onboarding]

    A ==> B
    C <==> B
    B e1@==> D
    D e2@<==> E
    D ==> F
    F ==> G
    G e3@==> H
    H e4@==> I
    J -. installs and configures .-> D
    J -. wires linked Arr clients .-> B

    classDef animate stroke-dasharray: 9,5,stroke-dashoffset: 900,animation: dash 25s linear infinite;
    class e1,e2,e3,e4 animate

The dashed arrows are DUMB automation. The solid arrows are the normal request and media flow after setup.

Service relationships¶

external_rclone does not create or start a DUMB-managed rclone instance. In that mode AltMount exposes its rclone RC service, while you remain responsible for the external mount process.

What AltMount provides¶

• A modern web UI and API for configuration, queue visibility, and health monitoring
• WebDAV access and range-based streaming directly from Usenet
• A SABnzbd-compatible download-client API for Arr applications
• Multiple NNTP providers with load distribution and failover
• Transparent handling of NZB content and supported archive formats
• NONE, SYMLINK, and STRM import strategies
• Built-in FUSE and rclone mount modes, plus an external-rclone mode
• Local metadata with optional SQLite-to-PostgreSQL migration through DUMB

AltMount owns the media-processing behavior. DUMB supplies the service lifecycle and integration around it.

What DUMB manages¶

Default port and URLs¶

The native port is inside the DUMB container. It is directly reachable from the host only if your deployment publishes or otherwise exposes it.

Configuration in dumb_config.json¶

The current default block is:

"altmount": {
  "enabled": false,
  "postgres_enabled": false,
  "postgres_database": "",
  "process_name": "AltMount",
  "repo_owner": "javi11",
  "repo_name": "altmount",
  "pinned_version": "latest",
  "suppress_logging": false,
  "log_level": "INFO",
  "port": 8088,
  "auto_update": false,
  "auto_update_interval": 24,
  "auto_update_start_time": "04:00",
  "mount_type": "rclone",
  "config_dir": "/altmount",
  "config_file": "/altmount/config.yaml",
  "metadata_dir": "/altmount/metadata",
  "mount_path": "/mnt/debrid/altmount",
  "log_file": "/altmount/logs/altmount.log",
  "command": [
    "/altmount/altmount",
    "serve",
    "--config",
    "/altmount/config.yaml"
  ],
  "env": {
    "PUID": "{puid}",
    "PGID": "{pgid}",
    "PORT": "{port}",
    "JWT_SECRET": "",
    "COOKIE_DOMAIN": "localhost",
    "ALTMOUNT_API_KEY": ""
  }
}

Important fields¶

• enabled: Starts AltMount under DUMB's process manager.
• pinned_version: Uses the latest upstream release or a specific release tag. DUMB installs the matching architecture-specific altmount-cli asset.
• port: Sets the native AltMount listener and is copied into env.PORT.
• mount_type: Selects DUMB's operator-facing mount mode.
• mount_path: Shared path where the selected internal mount is exposed; DUMB synchronizes this into AltMount's root-level configuration.
• config_dir, config_file, metadata_dir, log_file: Persistent paths managed by DUMB.
• auto_update, auto_update_interval, auto_update_start_time: Use DUMB's normal update scheduler.
• postgres_enabled, postgres_database: Select the optional PostgreSQL backend after completing the guarded migration workflow.
• env.JWT_SECRET, env.ALTMOUNT_API_KEY: Generated and saved by DUMB when blank. Treat both as secrets.
• env.COOKIE_DOMAIN: Defaults to localhost; change it only when your direct or reverse-proxied AltMount access model requires another cookie domain.

command, PUID, PGID, and PORT are reconciled by setup. Avoid treating them as independent AltMount UI settings.

Mount modes¶

DUMB creates /mnt/debrid/altmount by default and normalizes its ownership. During an install/update pass, DUMB also unmounts a stale FUSE mount at that exact path before replacing the AltMount binary. A non-FUSE mount is preserved rather than removed automatically.

Import strategy and library paths¶

Configure the import strategy in AltMount → Configuration → Import:

DUMB does not currently choose the import strategy, create its import_dir, or set Arr root folders/media-server libraries for AltMount. Keep every path inside the shared DUMB namespace—normally under /mnt/debrid—and make sure AltMount, the linked Arr, and the media server all see the same container path.

For SYMLINK or STRM, create and validate the chosen import directory before sending a real release. For NONE, confirm the linked Arr can browse the mounted category path under /mnt/debrid/altmount.

See AltMount's ARR integration guide for the application-level import and webhook options.

DUMB-to-AltMount Arr integration¶

For an enabled Sonarr, Radarr, Lidarr, or Whisparr instance, set:

"core_service": "altmount"

For a shared Arr instance that uses several workflow services, use a list or the equivalent comma-separated UI selection:

"core_service": ["decypharr", "infinidysk", "altmount"]

During guided onboarding, DUMB then:

1. Installs/configures AltMount and generates its internal secrets if needed.
2. Starts the selected Arr services and AltMount.
3. Reads each linked Arr API key from its application config.
4. Upserts the Arr instance URL/API key into AltMount's arrs section.
5. Enables AltMount's SABnzbd-compatible API and standard categories (movies, tv, music, and adult).
6. Creates or updates an altmount SABnzbd download client in each linked Arr with the matching category.

The integration is scoped by core_service; DUMB does not add every enabled Arr automatically. Existing AltMount Arr entries are updated by name or URL rather than replaced wholesale.

First-start checklist¶

1. Select AltMount as the Usenet workflow in guided onboarding, then choose its mount mode.
2. Open AltMount from the DUMB service page and create the first AltMount administrator account.
3. Replace the generated first-run WebDAV credentials (usenet / usenet) before exposing the endpoint outside a trusted network.
4. Add and test at least one TLS-enabled NNTP provider in AltMount.
5. Review the DUMB-selected mount type/path in AltMount's Mount settings.
6. Choose NONE, SYMLINK, or STRM and configure any required import directory.
7. Verify the linked Arr instances and their altmount download clients.
8. Send a small test NZB and confirm queue, import, library scan, and playback behavior end to end.

AIOStreams playback¶

AIOStreams can send matching NZBs to AltMount's SABnzbd-compatible API and serve the resulting WebDAV stream:

1. Enable AltMount's SAB API and copy its API key.
2. Create dedicated WebDAV credentials.
3. In AIOStreams, add AltMount under Services.
4. Use http://127.0.0.1:8088 for URL, replacing 8088 with AltMount's saved DUMB port.
5. Enter the API key and WebDAV credentials.
6. Prefer leaving Public URL blank and supplying an AIOStreams auth credential (username:password) whose user has Proxy permission. Use a direct Public URL only when AltMount has its own trusted HTTPS origin reachable by the player.

This does not change AltMount's DUMB-selected mount mode or Arr import strategy. AIOStreams communicates with the application API and WebDAV surface directly; never use its embedded /ui/altmount route as the service URL.

PostgreSQL migration¶

AltMount supports SQLite and PostgreSQL. New/default installs use /altmount/altmount.db.

For an existing SQLite-backed service, open Database Migration on the AltMount service page, run a rehearsal, validate the imported table counts against AltMount's application-created PostgreSQL schema, and only then run cutover. DUMB writes the PostgreSQL DSN into /altmount/config.yaml, registers the target database (altmount by default), and retains the SQLite file and migration backups for rollback.

Do not enable postgres_enabled directly when existing data must be retained. DUMB has not found an upstream application-specific data migration tool, so the guarded DUMB workflow and post-cutover application checks are important. See SQLite to PostgreSQL Migration.

Files and persistence¶

In the maintained Compose layout, back up /data/altmount (the persistence target behind internal /altmount) as sensitive application data. It can contain NNTP credentials, API keys, user data, and the SQLite database.

Embedded UI behavior¶

AltMount is a root-route React-style application. dmbdb keeps its root navigation and root /api/* calls in the AltMount iframe context so they do not collide with DUMB's own application or API routes. Open the UI from the AltMount service page rather than browsing directly to /ui/altmount.

If the embedded UI loses routing context, reload the DUMB service page. The direct Traefik-backed route is /service/ui/altmount when embedded service UIs are enabled.

Troubleshooting¶

AltMount does not start¶

• Check the DUMB service log and /altmount/logs/altmount.log.
• Confirm /altmount/altmount exists and is executable.
• Verify the configured port is free and /altmount/config.yaml is valid YAML.
• For FUSE/rclone modes, check whether /mnt/debrid/altmount is a stale, dangling, read-only, or busy mount path.

Provider or streaming failures¶

• Confirm at least one provider is enabled and its credentials, TLS mode, and connection limit are valid.
• Do not allocate more combined connections than the provider account permits.
• Review AltMount's queue and health pages for missing articles, masked files, or cache pressure.

Arr download-client setup is missing¶

• Confirm the Arr instance is enabled and core_service includes altmount.
• Confirm DUMB can read the Arr API key and AltMount's generated ALTMOUNT_API_KEY is still present.
• Verify both services are running, then restart AltMount or rerun the guided start so DUMB can repeat the integration pass.
• Check that the Arr category matches the DUMB defaults for its application type.

Import completes but the library cannot see the file¶

• Confirm mount_path, the AltMount import_dir, the Arr root folder, and the media-server library use paths visible inside the DUMB container.
• For SYMLINK, inspect the link target from inside the container and verify it remains under a shared path.
• For STRM, confirm the WebDAV URL written into the file is reachable by the player.
• Use Arr Manual Import to separate path visibility problems from download-client problems.

Embedded UI/API requests open DUMB instead of AltMount¶

• Reopen the AltMount service page and reload the iframe to refresh dumb_ui_service context.
• Verify embedded service UIs are enabled and /service/ui/altmount responds.
• Check dmbdb proxy logs for root-route or /api/* routing errors.

Related links¶

• AltMount documentation
• AltMount getting started
• AltMount ARR integration
• AltMount streaming configuration
• AltMount repository
• Core-service routing
• InfiniDysk
• Decypharr