Start free trial
Users can't connect to Foldr via WebDAV (Foldr Drive) · Self-hosted

Users can't connect to Foldr via WebDAV (Foldr Drive)

Updated 4 May 2026 Storage & Integrations Self-hosted only

Users can’t connect to Foldr via WebDAV (Foldr Drive)

Foldr exposes a WebDAV endpoint at /drive on the appliance. The Foldr desktop apps use it to mount the drive on Windows and macOS, and standalone WebDAV clients (Cyberduck, ForkLift, native Windows Map Network Drive, etc.) can connect there too. If users can’t reach it, work through the checks below in order: server-side first, then client-side.

Server-side checks (Foldr Settings)

Is the WebDAV endpoint enabled for non-Foldr clients?

By default the endpoint accepts only the Foldr desktop apps. To allow standalone WebDAV clients, an administrator turns on Other Clients under Foldr Settings → Devices → Configuration (“Allow users to connect using non-Foldr clients”).

Does the user’s account have access to Foldr Drive?

Under Foldr Settings → Security, check that the user’s Active Directory account, or one of their security groups, grants access to Foldr Drive. The default built-in group Foldr Users covers everyone unless an administrator has narrowed it.

Is the external hostname configured?

Some standalone WebDAV clients refuse to follow Foldr’s redirects unless the External hostname is set under Foldr Settings → Appliance. Without it, those clients see a hostname mismatch on the TLS certificate and abort.

Client-side checks

Are users using the right URL?

The WebDAV path is /drive, not the Foldr root. The full URL is https://your-foldr/drive. Standalone WebDAV clients usually have a separate Path field; put /drive there.

Windows: is the WebClient service running?

Windows ships with a built-in WebDAV client called WebClient that’s stopped by default on Server SKUs and on some hardened Pro deployments. From an admin command prompt:

sc query WebClient
sc config WebClient start= auto
net start WebClient

This is what the native Map Network Drive flow uses; without it, mapping a Foldr drive over WebDAV fails immediately.

macOS: which auth dialog are you stuck on?

Native macOS WebDAV via Connect to Server (Cmd+K) works against https://your-foldr/drive. If the prompt loops without accepting credentials, check whether two-factor authentication is enabled for the user. Native macOS WebDAV doesn’t handle 2FA prompts; for those users, use the Foldr macOS app instead.

When checks pass but it still fails

Generate a server support bundle and send it to support along with the WebDAV client name and version, the exact error message, and the time of a failed connection so the activity log can be matched up.

← All articles