Access methods

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.

Important

Your FileRun password does not work with a WebDAV client. A client that asks you for a username and a password needs an app password, which you create with the Connect app option of the FileRun interface. The username it gives you is not your login name either, so use both values exactly as shown. An app that asks for your FileRun address instead, such as the desktop sync app, receives its own credentials when you approve it in the browser, and there is nothing for you to type. See App passwords.

WebDAV client programs tested with FileRun:

An example of the URL you need to use to access FileRun's WebDAV would be: https://amsterdam.demo.filerun.com/dav.php/ (for our online demo)

Important

Please note that the URL must contain the trailing slash character, after "dav.php".

Note

When using Nextcloud desktop sync app, the URL should be the root of your FileRun installation (example: https://amsterdam.demo.filerun.com). Do not append "/dav.php/" to it.

Windows: Connecting with Explorer🔗

Please note that Windows will not connect to your server if it is not serving via HTTPS with a valid SSL certificate.

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: https://www.your-website.com/filerun**/dav.php/** (The highlighted part is the important part which needs to be appended to the FileRun URL)
4. You will be prompted for a username and a password. Use the two values given by the Connect app option of the FileRun interface, next to the Sign out option. Your own account name and password are not accepted. See App passwords.

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

If the above fails, try also this method:

1. Open a "Command Prompt"
2. Run net use * https://www.your-website.com/filerun/dav.php/ (Replace with your actual URL)

MacOS: Connecting with Finder🔗

Assuming your FileRun instance is installed at https://your-site.com/filerun/

In the Finder, choose Go → Connect to Server, type the address of the server in the Server Address field, and click Connect. For our example, that would be:

https://your-site.com/filerun/dav.php/

rclone🔗

When configuring FileRun to be used with rclone, make sure you use it in Nextcloud mode with the URL configured like this:

 1https://cloud.YOURDOMAIN.com/remote.php/dav/files/USERNAME/

This will have rcloud preserve the files modification times when syncing to FileRun.

Tip: use the –create-empty-src-dirs command flag to make sure rclone preserves empty folders.

Linux: mounting from the command line🔗

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

 1sudo apt-get install davfs2

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

 1sudo dpkg-reconfigure davfs2

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

 1sudo 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):

 1your-site.com/filerun/dav.php/ /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 the username and the password given by Connect app):

 1your-site.com/filerun/dav.php/ <username> <password>

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

 1chmod 600 ~/.davfs2/secrets

Run the command:

 1mount ~/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:

 1use_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:

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

Troubleshooting🔗

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:

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

NGINX - No XML🔗

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" into 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 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 the 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.