↑↓ to navigate ↵ to open Esc to close Search by Algolia

Updating to FileRun 2026.1

The tasks to do before and after applying the FileRun 2026.1.0 update: the database server, the Docker image, the NGINX configuration, the PHP and ionCube versions, the cron jobs and the settings that need a change. The changes of the version are listed on FileRun 2026.1.0.

1. Things you need to do before updating

  • Make a full backup of your installation. This will allow you to restore the installation to the previously working state in case something goes wrong. Ignore this at your own risk.
  • Make sure you are using MySQL 8.4 or higher, or MariaDB 10.11 or higher. FileRun will no longer work with versions older than that. See below for a tip on how to update the database server.
  • Archive the user activity logs if you wish to keep a copy of the old entries. This update will completely remove them.
  • Install this update outside working hours: File uploads that have been started before installing this update will not be able to resume after the update, and they will restart from the beginning.
  • Run the queued e-mail notifications. E-mail notifications will not be sent for user activity performed before installing this update, so make sure you run the notifications before installing the update, if any are queued. You can do so by clicking the button Manually run notifications now under the E-mail control panel section, or by running the command line script for sending notifications (see this documentation page).
  • Write down the FileRun license key. You can find it under the FileRun control panel section or get it from your FileRun client account.
  • If you encounter database errors during the update, try to restart/reboot your MySQL/MariaDB server/container and then try the update again. The reason why this works is that this update converts the database engine used in some of FileRun tables.

For users of the official FileRun Docker image:

  1. Update the database server:

Update MariaDB

  • Replace the server with version 10.11 or higher. We recommend you to use the latest version.
  • When using Docker, you can start the container with MARIADB_AUTO_UPGRADE=1
  • Or upgrade the databases by running mysql_upgrade.

Update MySQL

  • Replace the server with version 8.4 or higher. We recommend you to use the latest version.
  • Then upgrade the databases by running mysql_upgrade.
  1. Install the FileRun update from the FileRun control panel.
  2. Replace the Docker image with filerun/filerun
  3. Restart the container.

If you are running NGINX

Make sure that your configuration location ~ \.php$ is updated to the regex version location ~ ^(.+\.php)(.*)$ which allows URLs like /index.php/sub/path. This regex captures both the PHP file and the PATH_INFO portion.

  • Make sure your location block contains the following two lines: 
     1fastcgi_split_path_info ^(.+\.php)(.*)$;
 2fastcgi_param PATH_INFO $fastcgi_path_info;

Without this, the new FileRun version will not function at all.

2. Things you need to do after updating

  • Make sure PHP is version 8.2, 8.3 or 8.4 (recommended).
  • Make sure the PHP extension ionCube loader is version 14.4 or higher (15.0 recommended). Guide here.
  • If you are using a third-party OAuth2-based authentication, you will need to update the SSO redirect URL to https://FILERUN/index.php/app/Core/auth/!public/sso. You will find your precise URL under the Authentication control panel section.
  • Configure your HTTP server to block access to .php files inside the /apps folder. FileRun applies a .htaccess file for Apache and a web.config file for ISS. For NGINX, see the file /apps/security.nginx on suggested configuration that you will need to set in your NGINX configuration.
    • Test to make sure .php files are not accessible via the web server.
  • Configure your HTTP server to block access to the folder /system. FileRun applies a .htaccess file for Apache and a web.config file for ISS. For NGINX, see the file /apps/security.nginx on suggested configuration that you will need to set in your NGINX configuration.
    • Test to make sure the folder is not accessible via the web server.
  • If you are using the official FileRun Docker image, you will need to update the Path to LibreOffice binary to soffice. The setting can be found under the Thumbnails and preview control panel section. The manual change is required because the new docker image comes with a newer LibreOffice version.
  • If you are not using the official FileRun Docker image, you need to manually configure these cron jobs:
    • cron/email_notifications.php (as often as you need), for sending e-mail notifications. (For avoiding slowing down or breaking the user experience, notifications can no longer be sent in real-time.) More details here.
    • cron/every5minutes.php every 5 minutes. It clears inactive sessions.
    • cron/everyMinute.php every minute. It imports metadata from new files and sets files types (for filtering and searching).
    • cron/daily.php (once a day). It deactivates expired and inactive user accounts, and deletes guest accounts that have no shares anymore. It archives old log entries. It keeps the FileRun's database clean.
  • Review your theme customizations. Changes have been made to the theme, so unless you have made extensive customizations, it is recommended to press the Reset all to default button under Interface → Branding → Themes control panel section, and then reapply the color theme of your choice.
  • If you are using the ONLYOFFICE plugin: You will need to enable WOPI in your ONLYOFFICE DocumentServer: see https://api.onlyoffice.com/docs/docs-api/more-information/faq/using-wopi/ and https://api.onlyoffice.com/docs/docs-api/using-wopi/overview/#enabling-wopi
  • If you use the plugin Google Editor: The Authorized redirect URI for Google OAuth 2.0 Client IDs changed and needs to be updated. See this page.
  • If you have any custom event script, know that the new FileRun version will run these only for events defined by $config['system']['custom_event_scripts'] = []; inside customizables/config.php.
  • If the logo URL was set with a relative URL, you will need to adjust it to use an absolute URL. For the FileRun logo, just type FileRun (case-sensitive) in the URL fields.
  • To customize the favicons, please see this page.