Work through the connection in order: server, endpoint, authentication, directory listing, then audio playback. Fixing the first failing step usually gives a clearer answer than changing several settings at once. Keep credentials out of screenshots and shared logs.
Quick checks
- Can you open the server’s web interface from the same network?
- Is the URL a WebDAV endpoint, such as OpenList’s
/dav/, rather than an admin page? - Does the account have read access to the mounted music folder?
- Does the server list the expected tracks through WebDAV?
- Can OFPlayer test the connection, list tracks, and play one file?
Cannot reach the server
Check that the service or container is running and listening on the intended port. For Docker, use docker compose ps and docker compose logs. Confirm the host IP, port mapping, firewall, DNS, and reverse proxy. Try the server on the LAN before debugging an external domain. A timeout points to routing, firewall, or a stalled service; a quick HTTP error means the request reached something and should be inspected at that layer.
Login fails
An HTTP 401 usually means the credentials are missing or rejected; 403 often means the account lacks permission. Test the same account in the server UI, then verify its WebDAV Read permission and any mount-level access. Do not put a password into a URL or shell history just to test it. If you changed the password recently, update the saved OFPlayer connection.
Connected but the music folder is empty
Confirm the physical music folder is mounted inside the server, then inspect its virtual mount path. A WebDAV URL that already ends in /dav/music should not receive another /music in OFPlayer’s root path. Verify that the account can list both the parent and the mounted directory. An HTTP 404 points to a bad route or path; an empty successful listing often points to the wrong folder or permissions.
Tracks appear but playback fails
Listing and playback are separate requests. Check that the original audio file still exists and can be read, the media URL has not expired, and the server can return its bytes. Compare a small, known-good MP3 with a failing file. If only one format fails, inspect its actual codec with a media inspection tool; an extension alone does not prove decodability. If the web player fails but the Windows app works, inspect CORS and browser network errors.
Slow listings or buffering
Measure server CPU, storage latency, and network throughput. Try a small directory and one local-network client to isolate a slow remote mount or proxy. If audio buffers but listings are fast, inspect media response time and range-request behavior. Large remote libraries in the WinUI preview are subject to a 5,000-track loading cap; repeated Load more clicks cannot turn that into unlimited pagination.
WebDAV-specific errors
Directory browsing uses WebDAV methods such as PROPFIND. A reverse proxy or security rule that blocks those methods can allow the admin website to load while the music client fails. Confirm the proxy forwards the method and preserves authorization. Validate TLS certificates instead of disabling certificate checks for a public connection.
Collect useful evidence
Record the OFPlayer version, server software and version, whether the failure occurs at test/list/play, the HTTP status, and a sanitized server log excerpt. Remove host secrets, usernames if private, passwords, tokens, and personal paths. For setup steps, see OpenList, Navidrome, or OFPlayer connection.