I have found an easy alternative fix with Tiny File Manager.
Follow these steps under, just change domain.ltd with own domain.

  1. Create a new site, remeber DNS: "sudo wo site create files.domain.ltd --php83 --le"
  2. Then download Tiny File Manager: sudo wget -P /var/www/files.**domain.ltd** https://github.com/prasathmani/tinyfilemanager/archive/refs/tags/2.5.0.zip
    Install unzip: "sudo apt-get install unzip"
    unzip: "sudo unzip /var/www/files.domain.ltd 2.5.0.zip -d /var/www/files.domain.ltd"
    then copy tinyfilemanager.php to www folder: sudo cp /var/www/files.**domain.ltd**/tinyfilemanager-2.5.0/tinyfilemanager.php /var/www/
  3. Edit nginx config for site: "sudo site edit files.domain.ltd", and change root to /var/www/
  4. Add tinyfilemanager.php to index in nginx config OR rename tinyfilemanager.php to index.php
  5. You can now access Tiny File Manager, at files.domain.ltd
  6. Default username/password: admin/admin@123 and user/12345.

⚠️ Warning: Please set your own username and password in $auth_users before use. password is encrypted with password_hash(). to generate new password hash here

To enable/disable authentication set $use_auth to true or false.

You can edit username and password with: "sudo nano /var/www/tinyfilemanager.php" or if you renamed to index.php "sudo nano /var/www/index.php"

  1. You can now delete tinyfilemanager-2.5.0 folder inside files.domain.ltd with Tiny File Manager

Best of luck!

    I genuinely want to understand why you need a file browser. For non-technical users, I typically provide access to the server via FTP/SFTP

      corus9

      Cause i use multiple workstations and computers, and dont want to install a SFTP client every time i would like to change or upload something. So much easier with a web based file browser. FTP access to production sites i would not even consider, I would maybe use FTP to access files on a test server.

        ftp is inbult in wordops via proftpd stack and very easy to use with filezilla just requires 3-4 steps
        ive tried eXtplorer earlier when it was working but always found easy to use filezilla due to native layout and drag and drop file transfer for ease of use

          14 days later

          corus9

          I know proftpd is built in with wordops, but I would rather not use FTP. I don't even have port 20-21 open. I have port 22 forwarded to another port for SSH and SFTP. I would never transfer files on an unencrypted protocol.

            10 days later

            bigsneip Wondering if you have issues where uploads greater than a certain size are automatically being split into different files? I have been looking to find where this limit is set but did not find yet.

                blarg3891 Actually I figured it out. I saw errors about chunking and just disabled this feature. Its working now.

                in tinyfilemanager.php

                chunking: false
                forceChunking: false

                  25 days later

                  bigsneip

                  bigsneip

                  I modified your guide because it is safer to put tinyfilemanager inside port 22222.

                  This is how:
                  Download the file and Chmod the file as www-data:www-data
                  Put it in /var/www/22222/htdocs/files/

                  Edit the file:
                  From $root_path = $_SERVER['DOCUMENT_ROOT']; to
                  $root_path = '/var/www/';

                  From $http_host = $_SERVER['HTTP_HOST']; to $http_host = https://hostname.domain.tld:22222

                  And you can access the file manager as usual.

                  Works great so far.

                      3 months later

                      File Browser Installation and Configuration Guide
                      This guide provides step-by-step instructions to install and configure File Browser as an alternative to eXtplorer. It covers installation, service configuration, firewall settings, and troubleshooting.

                      Installation
                      Step 1: Update System Packages
                      Run the following command to update and upgrade your system packages:

                      sudo apt update && sudo apt upgrade -y

                      Step 2: Install File Browser
                      Use the following command to download and install File Browser:
                      curl -fsSL https://raw.githubusercontent.com/filebrowser/get/master/get.sh | bash

                      Step 3: Verify Installation
                      Check if File Browser is installed correctly:
                      filebrowser version

                      Configuration
                      Step 4: Set Up the Working Directory
                      Create the necessary directory and assign proper permissions:
                      sudo mkdir -p /var/www
                      sudo chmod 755 /var/www
                      sudo chown $(whoami):$(whoami) /var/www

                      Step 5: Start File Browser Manually (For Testing)
                      Run the following command to start File Browser:
                      filebrowser -r /var/www/ -d /var/www/filebrowser.db -a 0.0.0.0 -p 8081

                      If it works correctly, press Ctrl+C to stop and proceed with configuring it as a service.

                      Running File Browser as a Service
                      Step 6: Create a Systemd Service File
                      Open the systemd service configuration file:
                      sudo nano /etc/systemd/system/filebrowser.service

                      Add the following content:

                      [Unit]
                      Description=File Browser
                      After=network.target

                      [Service]
                      ExecStart=/usr/local/bin/filebrowser -r /var/www/ -d /var/www/filebrowser.db -a 0.0.0.0 -p 8081
                      Restart=always
                      User=root

                      [Install]
                      WantedBy=multi-user.target

                      Step 7: Enable and Start the Service
                      Run the following commands to apply and start the service:
                      sudo systemctl daemon-reload
                      sudo systemctl enable filebrowser
                      sudo systemctl start filebrowser
                      sudo systemctl status filebrowser

                      You should see the status as active (running).

                      Firewall Configuration
                      Step 8: Check Firewall Status
                      sudo ufw status

                      Step 9: Allow Access from Specific IPs
                      Replace the IP addresses with your own:
                      sudo ufw allow from 111.222.33.444 to any port 8081

                      Step 10: Reload Firewall Rules
                      sudo ufw reload

                      Troubleshooting
                      Restarting and Stopping File Browser Service
                      sudo systemctl restart filebrowser
                      sudo systemctl stop filebrowser
                      sudo journalctl -u filebrowser
                      sudo systemctl restart filebrowser

                      Following these steps, you will have a fully functional File Browser instance running as an alternative to eXtplorer. Ensure you configure the firewall settings properly for secure access. If you encounter issues, refer to the logs for debugging.

                      ACCESS: http://IPSERVER:8081

                        22 days later

                        deludwig16

                        Tested this with a new Ubuntu instance, works great with NGINX Proxy Manager. Only thing I noticed is that if you make new sites with WordOps you have to make sure Filebrowser has permission to the new folder inside /var/www

                          Hosted by VirtuBox