Managing files on servers with File Browser before the end of support

Introduction to File Browser

File Browser is an open-source application that provides a web graphical interface for managing files on a server. It allows users to access a directory and view it in almost any modern browser without the need to log in via SSH or use the command line.

This tool is particularly useful for those managing servers or self-hosted services, offering an experience similar to a desktop file manager but accessible via a browser. It is ideal for system administrators, developers, and advanced users who need an intuitive interface for managing remote files.

With File Browser, users can navigate folders, upload and download files, create directories, rename or move content, delete files, preview supported formats, and edit text files directly from the browser.

The project has been one of the most recognized in the self-hosting sector, with an active community and widespread use. However, active maintenance of the project has ended, and the final version is File Browser 2.63.23.

Prerequisites

• Hardware: A server or device with sufficient disk space for the files to be managed.
• Software: A compatible operating system (Linux, Windows, macOS).
• File Browser 2.63.23: Downloadable from the official repository.
• Docker (optional): To run File Browser in a container.
• Reverse Proxy (optional): To enhance security, such as Nginx or Apache.

Procedure to Install and Configure File Browser 2.63.23

This guide will allow you to install and configure File Browser 2.63.23, the last version of the popular open-source file manager.

Requirements

• A server with SSH access
• Docker installed on the server
• A domain or public IP address

1. Access your server via SSH: Open a terminal and connect to your server using the command:

   ssh user@serveripaddress

2. Download the File Browser Docker image: Run the following command to download the Docker image:

   docker pull filebrowser/filebrowser:2.63.23

3. Create a directory for configuration files: Run the command:

   mkdir -p /opt/filebrowser/config

4. Create a configuration file: Use a text editor like nano to create the configuration file:

   nano /opt/filebrowser/config/config.json

   Insert the following basic configuration:

   
   { "port": 8080, "baseURL": "", "root": "/srv", "tls": { "cert": "", "key": "" }
   } 

   Save and close the file by pressing Ctrl + X, then Y and Enter.
5. Configure the reverse proxy: If you want to expose File Browser through a domain, configure a reverse proxy like Nginx or Apache. Here is an example configuration for Nginx:

   
   server { listen 80; servername your-domain.com; location / { proxypass http://localhost:8080; proxysetheader Host $host; proxysetheader X-Real-IP $remoteaddr; proxysetheader X-Forwarded-For $proxyaddxforwardedfor; proxysetheader X-Forwarded-Proto $scheme; }
   } 

6. Access File Browser: Open a web browser and visit your server or domain address. You should see the File Browser interface. The default username is admin and the password is admin. You will be prompted to change it on first access.

By following these steps, you will have installed and configured File Browser 2.63.23 on your server.

Verification and Troubleshooting

At the end of this guide, you will be able to test the correct operation of File Browser and solve any problems.

Functionality Test

• Accessing the web interface: Open a browser and access the IP address of the server where File Browser is installed. Verify that the graphical interface is accessible and that there are no loading errors.
• Basic operations: Try performing fundamental operations such as navigating folders, uploading and downloading files, creating directories, renaming or moving content, deleting files, and previewing supported formats.
• Editing text files: Verify the ability to edit text files directly from the web interface without having to access the server via SSH or use the command line.

Troubleshooting

• Upload issues: If uploads freeze or hang, ensure you are using version 2.63.22 or later, which includes a fix for this issue.
• Non-scrollable sidebar: If the sidebar content exceeds the available space and is not scrollable, update to a version that includes this fix.
• Authentication problems: Verify that proxy tokens are not expired and that access rules are correctly applied during recursive operations.
• Exposure to the Internet: Do not directly expose File Browser to the Internet. Use a reverse proxy that handles TLS and an additional layer of authentication.
• Running commands: Keep command execution disabled and run the application as a non-privileged user, preferably within a container.
• Accessing directories: Mount only the specific directories that File Browser needs to access.

If problems persist, consider migrating to an alternative like Filebrowser Quantum, mentioned as a good replacement.

At the end of this guide, you will have understood the importance of File Browser and the implications of its cessation of support.

• File Browser remains a lightweight application for file management via web interface, useful for those who do not want to use SSH or the command line.
• Existing versions and Docker images will remain available, but the application will become unsupported software.
• The latest fixes include resolving upload issues, scrollable sidebar, and correcting access rules.

Invitation to Practice

If you decide to continue using File Browser after the end of support, follow these recommendations:

If you are a developer interested in continuing the development of File Browser, you can fork the repository and publish your versions, using the existing documentation as a guide.