Skip to content

AltMount

AltMount is a core Usenet-focused service that can provide a WebDAV interface, SABnzbd-compatible download-client behavior, metadata storage, and optional rclone mount management. In DUMB it is treated as a core Usenet workflow service so guided onboarding can wire Arr instances to it alongside or instead of NzbDAV.

What It Provides

AltMount provides:

  • A web UI and API on the configured service port
  • A WebDAV-style content endpoint for Usenet-backed media workflows
  • SABnzbd-compatible behavior for Arr download-client style integrations
  • Local metadata storage under the configured metadata directory
  • Optional rclone mount management from AltMount's own config

Default Ports

Service Port
AltMount 8088

DUMB checks http://127.0.0.1:8088/live by default to confirm the service is ready.

DUMB Configuration

The default DUMB config block looks like this:

{
  "altmount": {
    "enabled": false,
    "process_name": "AltMount",
    "repo_owner": "javi11",
    "repo_name": "altmount",
    "pinned_version": "latest",
    "port": 8088,
    "config_dir": "/altmount",
    "config_file": "/altmount/config.yaml",
    "metadata_dir": "/altmount/metadata",
    "log_file": "/altmount/logs/altmount.log",
    "wait_for_url": "http://127.0.0.1:8088/live"
  }
}

DUMB downloads the matching Linux release binary into /altmount/altmount, writes /altmount/version.txt, creates the metadata/log/rclone directories, and creates /altmount/config.yaml only when it does not already exist. Existing AltMount config files are left in place so UI or manual edits are preserved.

First Start

  1. Select AltMount as the Usenet workflow service in guided onboarding, or enable altmount in runtime config.
  2. Start the service from DUMB.
  3. Open the embedded UI from the AltMount service page or browse to http://<host>:8088.
  4. Configure providers, SABnzbd behavior, Arr integration, and rclone settings in AltMount.

DUMB enables AltMount SABnzbd compatibility, adds linked Arr instances to AltMount config, and registers AltMount as a SABnzbd download client in Arr instances whose core_service includes altmount. The generated first-run config intentionally leaves providers empty. Add provider details in AltMount before expecting download or WebDAV workflows to return content.

Files and Persistence

Path Purpose
/altmount/altmount Release binary downloaded by DUMB
/altmount/config.yaml AltMount runtime config
/altmount/metadata AltMount metadata root
/altmount/logs/altmount.log AltMount service log
/altmount/version.txt DUMB-managed installed version marker

Embedded UI

AltMount is available through the DUMB embedded UI proxy at /service/ui/altmount when enabled. Its root /api/* calls are routed to the AltMount service context so they do not collide with DUMB backend API routes.

Troubleshooting

  • If the service does not start, check /altmount/logs/altmount.log and the DUMB service logs.
  • If the UI loads but providers do nothing, verify providers are configured in /altmount/config.yaml or through the AltMount UI.
  • If the embedded UI sends API calls to DUMB instead of AltMount, refresh the service page so the embedded UI context cookie is reset.
  • If you pin pinned_version, include the release tag format used by upstream, such as v0.2.0.