AIMP WebDAV Cloud Not Working: How to Fix It

When the AIMP WebDAV cloud is not working, the visible symptom may be a failed connection, an empty folder, a playlist that refuses to load, or a track that appears but will not play. These symptoms usually come from one of five areas: an incorrect WebDAV endpoint, rejected credentials, an SSL certificate problem, insufficient directory permissions, or a server that is responding too slowly while listing or reading files. AIMP settings and Android restrictions can also contribute, but WebDAV should be tested first so you do not waste time changing audio output, skins, codecs, or unrelated player options.

The safest troubleshooting method is to start with one small folder and one known-good audio file. Confirm each layer separately: server access, folder listing, file download, playlist entry, and playback. Once a step works, stop changing that part of the setup and move to the next layer.

1. Confirm the Symptom With a Small Safe Test

Before editing your main playlist or cloud configuration, create a test folder on the WebDAV server. Put one ordinary MP3 or FLAC file in it, preferably a short file that already plays correctly from local storage in AIMP. Use a simple filename such as test.mp3 and avoid unusual symbols during this first test.

Then try to open that folder through AIMP and add only the test track to a new temporary playlist. This separates WebDAV access from problems involving a large music collection, old playlist paths, unusual filenames, embedded artwork, or slow metadata scanning.

1.1 Identify Exactly Where the Test Fails

• The connection cannot be saved or opened: Check the endpoint, credentials, authentication method, certificate, and network reachability.
• The account connects but the folder is empty: Check directory permissions, the selected path, server listing responses, and supported file visibility.
• The file appears but cannot be added: Create a clean playlist and verify that the file path has not been inherited from another device or account.
• The file enters the playlist but will not start: Test whether the complete file can be downloaded through another WebDAV client.
• Playback starts and then stops: Check connection stability, redirects, buffering, battery restrictions, and server-side timeouts.
• Only large folders fail: Allow the listing to finish or test a smaller directory with fewer files and subfolders.

Success means the test folder opens, test.mp3 appears, and playback begins without repeatedly requesting credentials. If that happens, the basic AIMP-to-WebDAV connection works. Stop changing the endpoint and account settings. The remaining problem is probably associated with the original folder, playlist, file, or library workflow.

2. Check the WebDAV Connection in AIMP

A WebDAV address is not always the same as the cloud provider's website address. A normal browser login page may use redirects, cookies, or interactive authentication that a WebDAV client cannot use. AIMP needs the provider's actual WebDAV endpoint.

2.1 Enter the Correct WebDAV Endpoint

Copy the endpoint from the cloud provider or server administrator rather than guessing it. Include the required HTTPS scheme, hostname, port, and path. Some services use a dedicated WebDAV hostname. Others use a path such as /dav, /webdav, or a user-specific directory. Nextcloud installations commonly expose authenticated WebDAV access below /remote.php/dav, but the exact file path depends on the account and server configuration.

Check for these common address mistakes:

• Using the cloud service's home page instead of its WebDAV endpoint
• Omitting a required path, port number, or username segment
• Entering HTTP when the server requires HTTPS
• Leaving an old endpoint in a playlist after the server address changed
• Using a public sharing link where authenticated WebDAV access is required
• Adding spaces or copying punctuation with the address

Success means AIMP can open the root or permitted starting folder without redirecting to a web login page. Once the correct folder appears, stop experimenting with address variations.

2.2 Recheck the Username and Password

Retype the username and password instead of relying on stored credentials. Check capitalization and make sure a mobile keyboard has not inserted a trailing space. Depending on the provider, the username may be an email address, a short account name, or a server-specific WebDAV login.

If the account uses two-factor authentication, single sign-on, or another interactive login system, the normal account password may not work in AIMP. Look in the provider's security settings for an app password, application token, or device-specific password. Create one specifically for AIMP if the provider supports it, then replace the stored password in the cloud connection.

Never paste credentials into public forums or screenshots. If a password has been exposed, revoke or change it before continuing.

Success means the server stops returning an authentication error and does not ask for the password again during the same test. At that point, do not reset the account or create additional app passwords unless authentication starts failing again.

2.3 Check Whether the Saved Cloud Entry Matches the Playlist

A saved playlist can contain remote references associated with an older cloud definition. This is especially important when transferring playlists between Windows and Android. Configure access to the same storage on each device, then rebuild a small playlist from the cloud entry on that device instead of assuming an imported playlist will automatically know which account to use.

Success means a track added from the newly configured cloud entry plays in a fresh playlist. If the fresh playlist works but the old one does not, keep the cloud configuration and replace or rebuild the stale playlist entries.

3. Check Certificates, Permissions, and Network Access

If the endpoint and credentials look correct, test the connection outside AIMP. A separate WebDAV client helps determine whether you have an AIMP troubleshooting problem or a server problem.

3.1 Test the Same Account With a WebDAV Client

Use a reputable WebDAV-capable file manager or desktop client. Enter the exact same endpoint, username, and app password. Try to perform four actions:

1. Open the configured starting directory.
2. List the test folder.
3. Download the small test track completely.
4. Open or play the downloaded local copy.

If another client cannot connect, AIMP is unlikely to be the root cause. Correct the server URL, credentials, certificate, permissions, firewall rule, reverse proxy, or WebDAV service configuration first. If the other client lists and downloads the file normally, return to AIMP and continue with a clean playlist test.

A web browser alone is not a complete WebDAV test. It may display a login page or download a file with a simple GET request while folder listing operations still fail.

3.2 Resolve SSL and Certificate Errors Safely

Use HTTPS whenever the server is accessed over the internet. WebDAV authentication should not be sent over an unprotected connection. If AIMP reports a certificate or secure-connection failure, verify that:

• The certificate is valid for the hostname in the WebDAV address.
• The certificate has not expired.
• The server supplies the required certificate chain.
• The device date and time are correct.
• The certificate authority is trusted by Windows or Android.
• A reverse proxy is presenting the intended certificate.

A self-signed certificate may work only after its issuing certificate is installed as trusted on the device, and some clients may still reject unusual or incomplete configurations. Do not permanently disable certificate validation or switch an internet-facing service to unencrypted HTTP merely to make the warning disappear. Correct the certificate or use a properly secured endpoint.

Success means the WebDAV client and AIMP connect without a certificate warning. Stop changing TLS settings after both accept the same HTTPS address.

3.3 Verify Directory and File Permissions

A successful login proves identity, not permission to read every folder. The WebDAV account needs permission to list the target directory and read the audio files inside it. With self-hosted storage, also check the underlying filesystem permissions and any share-level access rules.

A partially permitted account may show the root directory but not its contents. It may also list filenames while failing when AIMP requests the actual audio data. Test with a folder owned by the same account and grant only the access required for listening. Write or delete permission is not necessary if you only need playback.

Success means the independent WebDAV client can list and download the test file using the same account. If that works, stop broadening permissions. Excessive access will not improve playback and creates unnecessary risk.

3.4 Check Network Reachability and Redirects

Test AIMP on the same Wi-Fi network as the server, then test through the connection you normally use. If local access works but mobile data or external access does not, investigate router rules, VPN access, DNS, firewall configuration, reverse-proxy settings, and whether the server is intentionally limited to the local network.

A redirected download URL can also behave differently from the original WebDAV address. AIMP may list a directory successfully but fail when the server sends the audio request to another hostname, login page, or temporary URL. Compare the behavior with a dedicated WebDAV client and review the server or proxy logs if you control the service.

Do not disable Windows Defender Firewall, antivirus protection, or Android security controls permanently. If you suspect filtering, use the product's logs and create the narrowest appropriate rule for AIMP or the trusted server.

Success means the same small track works on the intended network without switching security tools off. Stop modifying network rules once that result is repeatable.

4. Check Folder Size, Playlist State, and File Compatibility

Large cloud folders can create a delay that looks like a failed connection. A WebDAV client may need to request the directory listing, parse many entries, and read metadata or artwork before the interface feels complete.

4.1 Reduce Large Folder Listing Delays

If a folder contains thousands of tracks, split it into smaller artist, album, or alphabetical directories. Start with 10 to 20 files and compare the loading time. Avoid repeatedly refreshing a folder while its first request is still in progress, because that can generate additional server work.

Embedded artwork and metadata can increase remote traffic when the player examines tracks. For the first test, use a file with modest tags and no unusually large embedded image. If the small folder loads immediately, the original connection is probably valid and the apparent failure is a scale or latency problem.

Success means the small folder becomes visible and responsive. Keep the working account and endpoint, then reorganize or load larger directories gradually instead of reinstalling AIMP.

4.2 Rebuild a Temporary Playlist

Create a new empty playlist and add the WebDAV test file directly from AIMP's cloud or file browser. Do not copy it from the failing playlist. Old remote playlist entries can preserve outdated paths, hostnames, account associations, or escaped characters.

If the temporary playlist works, remove only the broken entries from the original playlist or rebuild that playlist from the current cloud source. Do not delete every playlist until you have exported or backed up anything important.

Success means the newly added remote entry starts playing. That result confirms that the audio engine and WebDAV source can work together, so output methods, skins, and unrelated plugins should be left alone.

4.3 Do Not Expect Every Remote Folder to Enter the Music Library

A remote WebDAV playlist and the local music library are different workflows. On some AIMP configurations, remote tracks are intended to be added directly to playlists rather than indexed like files stored on the device. Full indexing can require extensive metadata reads across the network.

If the cloud folder opens in AIMP but does not appear in the library, add a few tracks directly to a playlist. If they play there, WebDAV is working and the library behavior should not be treated as a connection failure. A library rescan is useful for local folders that changed, but it is not a universal fix for remote WebDAV sources.

4.4 Test File Format and Source Quality

If one WebDAV track fails while others play, download that exact file with the test client and open the local copy in AIMP. If the local copy also fails, the issue is probably the file itself, its container, or its encoding rather than WebDAV.

If the local copy works but the remote version fails, compare the downloaded file size with the server's original and examine whether the connection stops early. Also test a basic MP3 or FLAC file. Do not install a general codec pack. AIMP includes support for many common audio formats, and codec packs do not repair WebDAV authentication, incomplete downloads, or incorrect server responses.

Success means the same file plays locally and remotely. Stop changing format or decoder options after that comparison passes.

5. Check Windows and Android Behavior Related to WebDAV

5.1 Windows Network and AIMP Checks

On Windows, confirm that AIMP is allowed to access the network and that the WebDAV hostname resolves to the expected server. If a VPN, proxy, filtered DNS service, or corporate network is active, repeat the small test on a normal trusted connection when permitted.

Audio output settings are relevant only if the remote track visibly plays while no sound is heard. In that case, test a local track in the same AIMP session. If local and WebDAV tracks are both silent, select the intended output device and check the Windows volume mixer. If local audio works but the WebDAV track never begins, return to the WebDAV and playlist checks instead of changing output modes.

A skin normally changes presentation, not server authentication. Switch temporarily to a built-in skin only if buttons, dialogs, or progress indicators are missing or inaccessible. Likewise, disable a third-party plugin temporarily only when the failure began after installing it or the plugin directly handles cloud access, playlists, networking, or audio processing.

The converter and tag editor are separate tools. Converter output options will not fix cloud streaming. Use File Information or the tag editor only to inspect whether a problematic file has unusual tags or oversized artwork after a simple file has already passed the WebDAV test.

5.2 Android Permissions and Background Restrictions

On Android, allow AIMP to use the network and any device permissions required for the files or services involved. Menu names vary by phone manufacturer, but check AIMP under the system's Apps settings for mobile data, Wi-Fi data, background data, battery usage, and storage or media access.

If playback stops when the screen turns off, when AIMP moves to the background, or after several minutes, temporarily set AIMP's battery use to unrestricted or exclude it from aggressive battery optimization. Also allow background data if Data Saver is preventing network activity. Some manufacturers add their own auto-start or background-app controls.

If the WebDAV server is on the local network, make sure the device remains connected to the correct Wi-Fi network and has any local-network permission required by its Android release. Storage permission affects local files and exported playlists, but it does not repair an incorrect remote endpoint.

Bluetooth is relevant only when playback is progressing but sound is routed incorrectly. Select the media-audio profile and test through the phone speaker. A Bluetooth profile cannot explain an empty WebDAV folder or an authentication error.

Success means the track continues through a screen-off and background test without interruption. Once it does, stop changing battery and data settings.

6. Use Logging and a Clean Temporary Test

If the simple checks do not reveal the cause, collect evidence before reinstalling the application. On AIMP for Android, logging may be available from the About dialog. Enable logging, restart AIMP, reproduce the problem once, note the approximate time, and inspect or share the resulting log through the official support channel. Remove or mask usernames, hostnames, tokens, and private paths when possible, but do not alter the error sequence.

Useful clues include authentication failures, certificate errors, timeouts, redirects, permission denials, incomplete responses, and file-not-found errors. A server administrator can compare the same timestamp with WebDAV, web server, or reverse-proxy logs.

6.1 Run a Controlled Clean Test

1. Back up important playlists and note the current WebDAV settings.
2. Create one new temporary playlist.
3. Use a test directory containing one known-good audio file.
4. Configure the verified HTTPS endpoint and the correct app password.
5. Open the directory and wait for the first listing to finish.
6. Add the track directly to the temporary playlist.
7. Play it on the active network, then repeat in the background if using Android.

If this controlled test succeeds, do not reinstall AIMP. Add your real folders gradually until the failure returns. The last folder, playlist, filename, or file added is then a useful lead.

If the clean test fails in AIMP but succeeds in another WebDAV client with identical details, check for an available stable AIMP update from the official site and search the official support forum for a matching server behavior. Provide the endpoint type, operating system, sanitized log, and precise reproduction steps. Never post a working password or access token.

Reinstallation should be a late step because it does not correct a wrong endpoint, revoked app password, invalid certificate, server permission, or reverse-proxy error. Avoid deleting playlists, clearing all app data, or changing many settings simultaneously until you have a backup and a reproducible test.

7. Quick Fix Checklist

• Confirm that the address is the real WebDAV endpoint, not a browser login page.
• Retype the username and use an app password when two-factor authentication is enabled.
• Use a valid HTTPS certificate matching the endpoint's hostname.
• Test directory listing and file download in a separate WebDAV client.
• Verify that the account can list the folder and read the audio file.
• Place one known-good MP3 or FLAC file in a small test folder.
• Add the test file to a new AIMP playlist instead of reusing an old entry.
• Wait for large folder listings and avoid repeated refresh requests.
• Try remote tracks directly in a playlist instead of assuming library indexing is required.
• Allow AIMP background data and relax battery restrictions if Android stops playback.
• Check output or Bluetooth only when playback advances but no sound is heard.
• Enable logging, restart AIMP, reproduce the issue once, and record the time.
• Reinstall only after the controlled test fails and your playlists are backed up.

8. Frequently Asked Questions

8.1 Why Does AIMP Accept My WebDAV Account but Show an Empty Folder?

The account may have permission to reach the server without permission to list that directory. The configured endpoint may also point to the wrong path, or a large listing may still be loading. Test the same folder with another WebDAV client and create a small directory containing one plainly named audio file.

8.2 Why Does My Normal Cloud Password Fail in AIMP?

Accounts protected by two-factor authentication or single sign-on often require an app password or device-specific token for WebDAV clients. Create one through the provider's account security page and use it in place of the interactive-login password.

8.3 Why Can I See a Track but Not Play It?

Listing a filename and reading the complete file are separate operations. The account may lack file-read permission, the server may redirect downloads incorrectly, the connection may time out, or the file may be damaged. Download the exact track through a WebDAV client and test the local copy in AIMP.

8.4 Should I Import WebDAV Music Into the AIMP Library?

Not necessarily. If the remote source opens, add tracks directly to an AIMP playlist first. Remote library indexing can involve extensive metadata access and may not behave like local-folder indexing. Successful playlist playback is enough to prove that the WebDAV connection works.

8.5 Can a Skin, Plugin, or Audio Output Setting Break WebDAV?

A cloud-related plugin can affect remote access, and a third-party skin can obscure controls, but ordinary skins and output methods do not usually cause authentication or directory-listing errors. Test with built-in components only when the problem began after a related change. Adjust audio output only if the track is visibly playing without sound.

8.6 When Should I Stop Troubleshooting AIMP and Contact the Server Provider?

Contact the provider or administrator when the same endpoint and credentials fail in a dedicated WebDAV client, the certificate is invalid, directory permissions are denied, or server requests time out. Contact AIMP support when the independent client can consistently list and download the test file but a clean AIMP playlist cannot access the same file. Include sanitized logs and exact reproduction steps.