WebDAV connections

Use WebDAV when your storage provider gives you a WebDAV address. FTPeach opens that location as a file pane so you can browse folders, upload and download files. A link that opens a website or its browser sign-in page is not necessarily a WebDAV endpoint.

On this page

Get the right address

Ask your provider for the full WebDAV URL, the username and the password to use with a file client. Include the provider's folder path, not just its hostname. Some services want a separate app password for file clients; get it from the provider first.

Example What to enter
https://files.example.com/dav/ A full HTTPS address, including the WebDAV folder.
https://files.example.com:8443/dav/ Include a custom port in the URL when the provider specifies one.
files.example.com Incomplete: add the scheme and the actual WebDAV path supplied by the provider.

Put credentials in Username and Password, not inside the address. FTPeach rejects addresses containing embedded credentials, a query (?) or a fragment (#). If the link you were given contains these, ask for the WebDAV endpoint rather than deleting pieces of the link and guessing.

Connect over HTTPS

  1. Open the source menu at the top of a pane and choose Server.
  2. Select WebDAV and paste the full URL into Address.
  3. Enter Username and Password. Leave Verify certificate enabled for HTTPS.
  4. Select Connect. When the folder listing appears, try a small file using Your first transfer.

WebDAV connection form showing a full HTTPS URL, username, password and Verify certificate enabled.WebDAV connection form showing a full HTTPS URL, username, password and Verify certificate enabled.

The path belongs in the address field.

FTPeach signs in with HTTP Basic authentication; HTTPS protects the connection carrying those credentials. A server that accepts only Digest authentication is unsupported and fails sign-in. Ask the administrator for an address that accepts Basic authentication.

For repeat visits, save a bookmark.

HTTPS certificates and plain HTTP

Keep Verify certificate enabled for HTTPS. If the provider uses a private certificate authority, the CA certificate button lets you select its trusted certificate file. Get the file and the server's hostname from the administrator. Turning verification off allows invalid certificates; it is not a repair for an incorrectly configured server.

An http:// address is different: the connection is unencrypted. By default, FTPeach does not send your password to it. It can follow a suitable upgrade to HTTPS on the same host and path, but does not treat a redirect to a different host as permission to send credentials there.

An HTTP WebDAV address with Allow unencrypted sign-in left unchecked.An HTTP WebDAV address with Allow unencrypted sign-in left unchecked.

Allow unencrypted sign-in appears for HTTP addresses. Leave it off and ask for an HTTPS endpoint. Enable it only if you deliberately accept sending the account credentials over plain HTTP. It is separate from Verify certificate: changing certificate verification does not authorize an unencrypted sign-in.

Transfers and permissions

WebDAV uploads do not offer Pause. If an upload is stopped, retrying starts it again from the beginning. Downloads can resume only when the remote version and the server's response make resuming safe; otherwise they restart. Read pause and resume behavior before stopping a large job.

Permission can differ between folders and operations. Being able to sign in or list files does not mean you may upload, replace or delete them. Ask the provider about the destination folder's permissions, quota and upload-size limits when an operation is refused.

When WebDAV does not connect

Message or symptom Next step
Enter the full WebDAV address, starting with http:// or https://. Use the provider's complete WebDAV URL, including the scheme and folder path.
A WebDAV address can't contain ? or # Ask for a WebDAV address rather than a browser-sharing or sign-in link. Enter credentials in their own fields.
Incorrect username or password. Confirm the WebDAV account details, any application-specific password requirement and the authentication method. Digest-only services are unsupported.
The server asks for a password over an unencrypted connection Ask for HTTPS. Use Allow unencrypted sign-in only if you accept the exposure described above.
The server's certificate isn't valid. Check the hostname and certificate with the provider, and ask for their CA file if they use their own.
The URL works in a browser, but FTPeach cannot list files Confirm that it is a WebDAV endpoint, not an HTML sign-in page or shared download link.
You don't have permission for this operation. Check this folder's permissions with the provider, even if signing in succeeded.

If you need help, include the exact error and operation, using the troubleshooting checklist. Remove passwords, tokens and private URL details before sharing anything.

Read this page on GitHub

Swipe to explore the enlarged image.