Accessing via WebDAV

As an alternative, FileRun can be also accessed with a standards-compliant WebDAV application. This can be useful for managing the remote files as they are folders on the local computer.

WebDAV client programs tested with FileRun:

Program NameOperating SystemLicenseNotes
Windows Explorer Windows Our opinion: only if you don't have other options
MacOS Finder Mac Our opinion: decent solution
Linux Linux
Cyberduck Windows
Free Our opinion: decent solution
WinScp Windows
GoodSync Windows
Free/Pro versions Good for two-ways folder synchronization
FE File Manager iOS Free Recommended by FileRun!
WebDAV Navigator iOS Free
WebDrive Windows
Free Trial Our opinion: very good!
NetDrive Windows
Free Trial Our opinion: very good!

An example of the URL you need to use to access FileRun's WebDAV would be: (for our online demo)

Please note that the URL must contain the trailing slash character, after “dav.php”.
When using Nextcloud desktop sync app, the URL should be the root of your FileRun installation (example: Do not append “/dav.php/” to it.
  1. Open This PC
  2. Right click the empty space and select Add a network location
  3. Type in the URL of your FileRun installation, like this: (The highlighted part is the important part which needs to be appended to the FileRun URL)
  4. You will be prompted for your FileRun account's username and password.
  5. Use the convenient Connect app option from the FileRun interface (next to the Sign out option in the FileRun menu) to generate credentials.

To mount My Files directly, append %40Home/ to the above URL.

Assuming your FileRun instance is installed at

In the Finder, choose Go > Connect to Server, type the address of the server in the Server Address field, and click Connect. The server address should be in a form similar to this: ADDRESS/filerun/dav.php/.

For our example, that would be:

Install the WebDAV support using the davfs package. On Debian/Ubuntu, you can use:

sudo apt-get install davfs2

Reconfigure davfs2 to allow access to normal users (select Yes when prompted):

sudo dpkg-reconfigure davfs2

Add the users you want to be able to mount the share to the davfs2 group:

sudo usermod -aG davfs2 <user>

Edit /etc/fstab and add the following line for each user who wants to mount the folder (with your details where appropriate): /home/<username>/filerun davfs user,rw,noauto 0 0

Then, as each user who wants to mount the folder:

Create the folders filerun/ and .davfs2/ in your home directory

Create the file secrets inside .davfs2/, fill it with the following (with your credentials where appropriate): <username> <password>

Ensure the file is only writable by you either through the file manager, or via:

chmod 600 ~/.davfs2/secrets

Run the command:

mount ~/filerun

To automatically mount the folder on login, add the command you used in step 4 to ./.coderc

Known Issues

Problem: Resource temporarily unavailable

Solution: If you experience trouble when you create a file in the directory, edit /etc/davfs2/davfs2.conf and add:

use_locks 0

Problem: Certificate warnings

Solution: If you use a self-signed certificate, you will get a warning. If you are willing to take the risk of a man in the middle attack, run this command instead:

echo "y" | mount ~/filerun > /dev/null 2>&1

Login loop

If the user credentials are not being accepted despite being correct, make sure the server environment variable “HTTP_AUTHORIZATION” is being populated by the web server. On Apache web servers, the configuration line would look like this:

SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1


The default NGINX with PHP-FPM configuration breaks URLs such as /dav.php/some/path. Please see this section:

IIS - 405 Method Not Allowed

Step 1: Open IIS Manager

Open the Start menu and type “IIS” in to the find box. You should see an application called Internet Information Services (IIS) Manager.

On the left, there is a Connections pane. You should see your computer listed here. Click on your computer name which should load the a dashboard with a handful of icons.

Step 2: Open PHP Handler Mapping

Double-click on the Handler Mappings icon to bring up the Handler Mappings screen.

Then double-click on the handler for PHP files to bring up the Edit Module Mapping window:

Step 3: Edit Verbs

Click on the Request Restrictions button, then switch to the [Verbs] tab. Switch the radio button to All Verbs, then click OK to close the window, then OK again to close the other window.

If the problem persists

  1. Open WebDav Authoring Rules and then select Disable WebDAV option present on the right bar.
  2. Select Modules, find the WebDAV Module and remove it.
  3. Select HandlerMapping, find the WebDAVHandler and remove it.
  4. Restart IIS.