AList WebDAV reference & migration

Audit an existing AList deployment, verify WebDAV permissions, and plan a safe move to OpenList.

Updated

Many self-hosted music libraries started with AList exposing a NAS folder over WebDAV. If you already have an AList instance running smoothly at home, you do not need to tear it down just to listen in OFPlayer—your existing WebDAV endpoint works right away once its path and permissions are verified.

For a brand-new server, start with the OpenList setup guide or the Navidrome setup guide instead. This guide is written specifically for existing AList deployments, helping you audit your current configuration for OFPlayer and plan a calm, reversible migration to community-maintained OpenList when you are ready.

[!NOTE] Reviewed in October 2026 for OFPlayer for Windows (26.0.6), OFPlayer for Android (26.0.2), and the web player. Always take a full backup of your configuration directory before altering an existing container or database.

1. Five details to record before changing anything

When working with a long-running server, take stock before touching any configuration files:

Item to check What to record Why it matters
1. Deployment type & version Docker (xhofe/alist), Windows binary, or NAS package, plus the exact version Determines where data lives and which migration steps apply
2. Data directory The host path mapped to /opt/alist/data (or local data/ folder) Holds your storage mounts and user accounts; back this up first
3. Physical & virtual paths Your real music folder on disk (e.g. D:\Music) and the virtual mount path (e.g. /music) Defines the exact WebDAV URL OFPlayer will request
4. Playback account & rights The username used by OFPlayer and whether WebDAV Read is enabled Prevents HTTP 403 errors and avoids sharing your admin login
5. Reverse proxy & TLS Nginx/Caddy configuration, domain name, and HTTPS certificates Lets you keep the same URL when switching backends later

2. Verify your existing WebDAV endpoint and permissions

Most connection hiccups on an older AList server come down to mixing up the web dashboard URL with the WebDAV protocol path:

  1. Check the storage mount status: Sign in to the AList admin UI (port 5244 by default) and open Storages. Confirm that your music storage status is work and that browsing the web UI lists your albums. If AList runs in Docker, consider marking the host music volume :ro (read-only) so your audio files can never be modified by the container.
  2. Separate the admin UI from /dav/: While you sign in at http://192.168.1.100:5244, WebDAV clients must connect under /dav/. If your storage mount path is /music, the full WebDAV address is:
    http://192.168.1.100:5244/dav/music
  3. Confirm WebDAV Read permission: Open Users in the admin dashboard and inspect the account you plan to use in OFPlayer. Verify that the account is enabled, its base path includes /music, and WebDAV Read is checked.

3. Connect your existing AList to OFPlayer

Once those checks pass, you can connect OFPlayer immediately without restarting your server:

  • In OFPlayer for Windows (26.0.6) or Android (26.0.2): Open the top-left source picker on Windows (or tap the add button in the library top bar → Music server on Android) and choose WebDAV.
  • Enter the endpoint and root path: Either set the Server URL to http://192.168.1.100:5244/dav and the Root path to /music, or put the full http://192.168.1.100:5244/dav/music in the Server URL and leave the Root path empty. Never put /music in both fields.
  • Test and save: Enter your username and password, run Test connection, and save.

[!TIP] If the connection works on Windows or Android but fails in the browser web player (/app), browser CORS rules are likely blocking the request. Use the native Windows or Android app, or see the WebDAV troubleshooting guide.

4. Plan a safe migration to OpenList

OpenList is the actively maintained community fork that preserves the familiar WebDAV workflow while continuing to ship security and stability updates. When migrating from AList to OpenList, avoid swapping container images in place without a backup:

  1. Archive your existing data directory:
    tar -czf alist-data-backup-$(date +%Y%m%d).tar.gz /path/to/alist/data
  2. Review the official migration notes and test in parallel: Check the OpenList migration guide for your specific AList version. Spin up OpenList using a copy of your data directory (or on a test port) following the OpenList setup guide, with your music folder mounted read-only (:ro).
  3. Switch over once paths match: After confirming that /dav/music lists and plays your tracks cleanly in the new OpenList instance, point your port mapping or reverse proxy to OpenList. If you keep the same /music mount path and credentials, your saved OFPlayer sources will continue working without reconfiguration.