This page is for people who already run AList and need to check their WebDAV connection before using OFPlayer or planning a migration. For a new server, start with OpenList and its current official documentation. Do not replace a working AList binary or database with an OpenList image without reviewing a supported migration path and taking a backup.
What to record before changing anything
- AList version and installation method: Windows binary, Docker, or NAS package.
- The configuration and database directory, plus a tested backup.
- Physical music directory and the virtual mount path shown in AList.
- WebDAV endpoint, account, and read permission.
- Reverse proxy, TLS certificate, and any external URL used by clients.
The administrative website and WebDAV endpoint are different paths. In common AList setups, the WebDAV root ends in /dav/, with a storage mount such as /music available under /dav/music. Confirm these paths against your actual server configuration instead of copying an example blindly.
Verify your existing music mount
Sign in to the AList admin UI and confirm that the music storage mount lists the expected files. If AList is in Docker, check that the host music directory is mapped into the container and that the process can read it. On a NAS, verify package permissions and the volume path. A successful admin login does not by itself prove the WebDAV account can read the folder.
Verify WebDAV access
Use a dedicated account with read access to the music mount. Test the WebDAV URL with a client you trust, then add it in OFPlayer as a WebDAV source with the correct endpoint, credentials, and optional root path. Avoid appending the same /music segment in both the endpoint and root field. Use HTTPS if the endpoint is accessible beyond a trusted LAN.
Organize and protect the files
A predictable artist/album folder structure and consistent embedded tags make browsing easier. Keep artwork and lyrics next to the music when your workflow uses sidecar files. Back up the original audio independently from the AList database. For remote access, restrict exposure at the firewall or proxy and keep the server updated through its supported channel.
If the connection fails
Check the service process, URL and port, WebDAV permission, virtual mount, and physical directory in that order. A 401 or 403 points toward authentication or authorization; a 404 usually points toward the endpoint or mount path. If the list appears but a song cannot play, inspect the media response and file permissions separately. See the WebDAV troubleshooting guide.
When moving to OpenList, follow the migration documentation for the versions you actually use. Back up configuration and music, test the new instance in isolation, then switch clients only after comparing the mount paths and playback behavior.