Once your NAS, OpenList, or Navidrome server is quietly humming in the background, the player takes over. Connecting a remote library in OFPlayer doesn’t copy gigabytes of audio onto your device up front—OFPlayer lists your folders or indexed albums first, and streams the original audio file only when you press play.
[!NOTE] Reviewed in October 2026 for OFPlayer for Windows (26.0.6), OFPlayer for Android (26.0.2), and the web player (
/app). Need to set up a server first? Start with the OpenList setup guide or Navidrome setup guide.
1. Check three details before connecting
A quick check of three details prevents almost every first-time connection error:
- Use the protocol endpoint, not the admin dashboard URL: The web page where you manage your server (such as
http://192.168.1.100:5244) is not the WebDAV endpoint. OpenList and AList serve WebDAV under/dav/(for example,http://192.168.1.100:5244/dav/music), while NAS appliances use their own dedicated WebDAV ports and paths. - Pick the matching source type: Choose WebDAV for OpenList, AList, or NAS WebDAV shares. Choose Subsonic for Navidrome and other Subsonic-compatible servers. On Windows, FTP is also available.
- Do not duplicate the folder path: OFPlayer combines the server endpoint and the optional Root path field. If your endpoint already ends in
/dav/music, leave the root path empty so the request does not become/dav/music/music.
| Server setup | Source type in OFPlayer | Example endpoint URL | Optional root path |
|---|---|---|---|
| OpenList / AList | WebDAV | http://192.168.1.100:5244/dav |
/music (leave empty if already in URL) |
| Synology / QNAP NAS | WebDAV | http://192.168.1.100:5005 |
/music (match your shared folder path) |
| Navidrome | Subsonic | http://192.168.1.100:4533 |
Leave empty; pick the library after connecting |
2. Add the source on Windows, Android, or the web
Your server address and credentials are stored locally on your device. OFPlayer connects straight to the server you configure—never through OFPlayer’s servers.
In OFPlayer for Windows (26.0.6)
- Open the source picker in the top-left corner and choose Add remote source… (or Add network library…).
- Give the connection a clear name, such as Home NAS or Living Room Navidrome.
- Select WebDAV, Subsonic, or FTP, then fill in the server URL, optional root path, username, and password.
- Click Test connection. Once it succeeds, save the source and select it from the source menu.
In OFPlayer for Android (26.0.2)
- From the top bar of the library view, tap to add music and choose a music server.
- Select WebDAV or Subsonic and enter the same endpoint, username, and password.
- Test the connection, save, and browse your remote folders or albums on your phone.
In the web player (/app): a note on CORS
The web player offers the same WebDAV and Subsonic connection options, but because it runs inside a browser tab, your server must explicitly allow cross-origin requests (Access-Control-Allow-Origin) and WebDAV methods.
[!TIP] If a server works in a normal browser tab or on Windows/Android but fails inside the OFPlayer web player, browser CORS policy or HTTPS/HTTP mixed-content rules are almost always the reason. Connecting with OFPlayer for Windows or OFPlayer for Android bypasses browser CORS restrictions entirely.
3. Why listing tracks and playing a track are two separate steps
It can feel puzzling when a connection test passes and your song list appears, yet clicking a track fails to play. Under the hood, remote playback happens in two distinct stages:
- Stage 1 — Directory enumeration: When you open the source, OFPlayer sends a
PROPFINDrequest (for WebDAV) or a catalog query (for Subsonic). A visible track list proves that the server can list filenames and metadata. - Stage 2 — Media stream resolution: Only when you select a song does OFPlayer request the actual audio stream. Missing source files, expired signed URLs, blocked
Rangerequests, or accounts that have directory-listing rights without file-read rights will surface at this step.
Also keep in mind that OFPlayer for Windows currently loads up to 5,000 tracks per remote list (Load more expands up to that cap rather than paginating infinitely). If your server holds a larger collection, a list stopping at 5,000 tracks simply reflects the current client cap, not missing files on disk.
4. Quick diagnosis by symptom
If something goes wrong, play one known-good local audio file first to rule out local output device issues, then match what you see:
| What you see | Where to look first |
|---|---|
| Connection test fails immediately | Server status, WebDAV /dav/ URL vs. admin page URL, port/firewall, and login credentials |
| Connected, but the track list is empty | Duplicate /music in endpoint + root path, WebDAV Read permission, or wrong library selected |
| Tracks appear, but clicking one will not play | Physical file existence, read permissions, redirected storage URLs, or unsupported legacy codecs |
| Works on Windows/Android, fails in web player | Missing CORS headers on the server or reverse proxy, or HTTPS-to-HTTP mixed content |
If your music already lives on a Windows PC and you simply want to listen from your Android phone around the house, you don’t even need a WebDAV server—open Settings → Devices on Windows to pair your phone and use LAN streaming and Handoff. For deeper server diagnostics, continue to the WebDAV troubleshooting guide and Remote music sources.