{"id":1141,"date":"2026-11-21T18:00:00","date_gmt":"2026-11-21T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1141"},"modified":"2026-11-21T18:00:00","modified_gmt":"2026-11-21T18:00:00","slug":"install-filerun-lamp-debian-11","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/21\/install-filerun-lamp-debian-11\/","title":{"rendered":"How to Install FileRun with LAMP on Debian 11"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install FileRun with LAMP on Debian 11 to turn a VPS into a private file manager with sharing, WebDAV, and browser access in about 25 minutes. This guide uses Apache, PHP 8.4, MariaDB 10.11, HTTPS, and a data directory outside the public web root.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>A 64-bit Debian GNU\/Linux 11 (Bullseye) VPS with at least 2 GB of RAM and enough disk space for both the application and your files.<\/li>\n\n\n<li>SSH access as <code>root<\/code>, or a normal account with working <code>sudo<\/code> privileges.<\/li>\n\n\n<li>A domain such as <code>YOUR_DOMAIN<\/code> with an A record pointing to the VPS. A domain is required for a trusted Let&#8217;s Encrypt certificate.<\/li>\n\n\n<li>A FileRun installation ZIP downloaded from the <a href=\"https:\/\/my.filerun.com\/client-area-orders\" target=\"_blank\" rel=\"noopener\">FileRun client area<\/a>, plus a strong superuser password and a separate MariaDB password.<\/li>\n\n\n<li>A <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> with a public IPv4 address is suitable for this LAMP deployment.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Debian 11 is no longer a current supported release, so use this procedure for an existing Bullseye server and plan an operating-system upgrade. The current FileRun requirements call for PHP 8.3\u20138.5, ionCube Loader, and MariaDB 10.11 or newer; Debian 11&#8217;s default packages are older, so the guide adds the vendor repositories where needed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The commands use <code>sudo<\/code>. If you are logged in as <code>root<\/code>, remove <code>sudo<\/code> from each command. Replace every uppercase placeholder before running its block.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Bullseye and install Apache<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Confirming the release avoids mixing Debian 11 packages with repositories for another Debian version.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -E '^(PRETTY_NAME|VERSION_CODENAME)=' \/etc\/os-release\ndpkg --print-architecture\nsudo sed -i -E 's#https?:\/\/(deb|security)\\.debian\\.org\/debian(-security)?#http:\/\/archive.debian.org\/debian#g; \/bullseye-security\/d' \/etc\/apt\/sources.list\nsudo apt -o Acquire::Check-Valid-Until=false update\nsudo apt install -y apache2 ca-certificates curl gnupg unzip ufw certbot python3-certbot-apache\nsudo systemctl enable --now apache2\nsudo systemctl is-active apache2<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output includes <code>VERSION_CODENAME=bullseye<\/code>, a 64-bit architecture such as <code>amd64<\/code>, and an active Apache service:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>VERSION_CODENAME=bullseye\namd64\nactive<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Install MariaDB 10.11 and PHP 8.4<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">FileRun needs a current database and PHP runtime, while Bullseye&#8217;s standard repository supplies MariaDB 10.5 and PHP 7.4.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Configure the official MariaDB 10.11 repository, then add the signed PHP repository for Bullseye:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -LsS https:\/\/r.mariadb.com\/downloads\/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version=\"mariadb-10.11\"\nsudo curl -fsSL https:\/\/packages.sury.org\/debsuryorg-archive-keyring.deb -o \/tmp\/debsuryorg-archive-keyring.deb\nsudo dpkg -i \/tmp\/debsuryorg-archive-keyring.deb\nsudo tee \/etc\/apt\/sources.list.d\/php.sources &gt;\/dev\/null &lt;&lt;'EOF'\nTypes: deb\nURIs: https:\/\/packages.sury.org\/php\/\nSuites: bullseye\nComponents: main\nArchitectures: amd64 arm64 armhf\nSigned-By: \/usr\/share\/keyrings\/deb.sury.org-php.gpg\nEOF\nsudo apt -o Acquire::Check-Valid-Until=false update\nsudo apt install -y mariadb-server mariadb-client php8.4 libapache2-mod-php8.4 php8.4-cli php8.4-mysql php8.4-curl php8.4-zip php8.4-xml php8.4-mbstring php8.4-imagick php8.4-gd\nsudo systemctl enable --now mariadb<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The PHP extensions cover database access, encrypted requests, archive handling, XML, multibyte text, and previews. FileRun&#8217;s <a href=\"https:\/\/docs.filerun.com\/requirements\" target=\"_blank\" rel=\"noopener\">requirements documentation<\/a> lists ionCube as required and ImageMagick as useful for thumbnails.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Set production-friendly PHP limits for the Apache SAPI and reload Apache:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/php\/8.4\/apache2\/conf.d\/99-filerun.ini &gt;\/dev\/null &lt;&lt;'EOF'\nmemory_limit = 256M\nmax_execution_time = 300\nupload_max_filesize = 1G\npost_max_size = 1G\ndisplay_errors = Off\nsession.cookie_httponly = On\nsession.cookie_secure = On\nEOF\nsudo systemctl restart apache2\nphp8.4 -v\nmariadb --version<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The version checks should show PHP 8.4 and MariaDB 10.11 or a later compatible release.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Install ionCube Loader<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">FileRun&#8217;s PHP files require the ionCube extension, which is distributed separately from Debian and PHP.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The command below downloads the official 64-bit Linux loader archive, enables the PHP 8.4 loader for both CLI and Apache, and confirms that PHP can see it:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/tmp\ncurl -fL https:\/\/downloads.ioncube.com\/loader_downloads\/ioncube_loaders_lin_x86-64.tar.gz -o ioncube_loaders.tar.gz\ntar -xzf ioncube_loaders.tar.gz\nsudo install -d -m 0755 \/usr\/local\/ioncube\nsudo install -m 0644 ioncube\/ioncube_loader_lin_8.4.so \/usr\/local\/ioncube\/\necho 'zend_extension=\/usr\/local\/ioncube\/ioncube_loader_lin_8.4.so' | sudo tee \/etc\/php\/8.4\/apache2\/conf.d\/00-ioncube.ini &gt;\/dev\/null\necho 'zend_extension=\/usr\/local\/ioncube\/ioncube_loader_lin_8.4.so' | sudo tee \/etc\/php\/8.4\/cli\/conf.d\/00-ioncube.ini &gt;\/dev\/null\nsudo systemctl restart apache2\nphp8.4 -i | grep -i -m 1 ionCube<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You should see a line identifying the ionCube Loader. Use the <a href=\"https:\/\/www.ioncube.com\/loaders.php\" target=\"_blank\" rel=\"noopener\">official ionCube loader page<\/a> if your VPS is ARM64 or another architecture; download the matching archive and loader file instead of using the x86-64 filename above.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Create the FileRun database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A separate database account limits the damage if the web application is compromised and keeps the MariaDB administrator login out of FileRun.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the hardening wizard and answer its prompts to remove anonymous users, remote root access, and the test database:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb-secure-installation<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Create the database and account. Replace <code>YOUR_DB_PASSWORD<\/code> with a long, unique password before running the block:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb &lt;&lt;'SQL'\nCREATE DATABASE filerun CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;\nCREATE USER 'filerun'@'localhost' IDENTIFIED BY 'YOUR_DB_PASSWORD';\nGRANT ALL PRIVILEGES ON filerun.* TO 'filerun'@'localhost';\nFLUSH PRIVILEGES;\nSQL<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The installer needs the temporary <code>ALTER<\/code> and <code>DROP<\/code> privileges included above. After the browser setup completes, remove those two privileges as shown in Step 7.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Download FileRun and configure Apache<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Keeping user files outside Apache&#8217;s document root prevents someone from bypassing FileRun&#8217;s access checks with a direct URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create the application and private storage directories. Download <code>FileRun.zip<\/code> from the client area, then upload it with SFTP to <code>\/var\/www\/filerun\/<\/code> before running the extraction commands:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo install -d -o www-data -g www-data -m 0755 \/var\/www\/filerun\nsudo install -d -o www-data -g www-data -m 0770 \/srv\/filerun-data\nsudo unzip -q \/var\/www\/filerun\/FileRun.zip -d \/var\/www\/filerun\nsudo rm -f \/var\/www\/filerun\/FileRun.zip\ntest -f \/var\/www\/filerun\/index.php &amp;&amp; echo \"FileRun files extracted\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Let Apache write during the first-run wizard, while keeping the private data directory inaccessible to other local users:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R www-data:www-data \/var\/www\/filerun\nsudo find \/var\/www\/filerun -type d -exec chmod 0755 {} +\nsudo find \/var\/www\/filerun -type f -exec chmod 0644 {} +\nsudo install -d -o www-data -g www-data -m 0770 \/var\/www\/filerun\/system\/data<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Create a virtual host for the domain. This also denies direct web access to FileRun&#8217;s internal <code>system<\/code> directory and PHP files beneath <code>apps<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/apache2\/sites-available\/YOUR_DOMAIN.conf &gt;\/dev\/null &lt;&lt;'APACHE'\n&lt;VirtualHost *:80&gt;\n    ServerName YOUR_DOMAIN\n    ServerAdmin YOUR_EMAIL\n    DocumentRoot \/var\/www\/filerun\n\n    &lt;Directory \/var\/www\/filerun&gt;\n        Options -Indexes +FollowSymLinks\n        AllowOverride All\n        Require all granted\n    &lt;\/Directory&gt;\n\n    &lt;Directory \/var\/www\/filerun\/system&gt;\n        Require all denied\n    &lt;\/Directory&gt;\n\n    &lt;Directory \/var\/www\/filerun\/apps&gt;\n        &lt;FilesMatch \"\\.php$\"&gt;\n            Require all denied\n        &lt;\/FilesMatch&gt;\n    &lt;\/Directory&gt;\n\n    ErrorLog ${APACHE_LOG_DIR}\/filerun_error.log\n    CustomLog ${APACHE_LOG_DIR}\/filerun_access.log combined\n&lt;\/VirtualHost&gt;\nAPACHE\nsudo a2dissite 000-default.conf\nsudo a2ensite YOUR_DOMAIN.conf\nsudo a2enmod rewrite headers\nsudo apache2ctl configtest\nsudo systemctl reload apache2<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>YOUR_DOMAIN<\/code> and <code>YOUR_EMAIL<\/code>. <code>Syntax OK<\/code> means Apache accepted the configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Open the firewall and enable HTTPS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Allow SSH before enabling UFW, then expose only the ports needed for administration and web traffic.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ufw allow OpenSSH\nsudo ufw allow 80\/tcp\nsudo ufw allow 443\/tcp\nsudo ufw --force enable\nsudo ufw status verbose<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The status should show active rules for SSH, 80, and 443. If SSH uses a custom port, allow that port instead of <code>OpenSSH<\/code>; the <a href=\"https:\/\/vpslake.com\/ufw-firewall-generator\">VPSLake UFW firewall generator<\/a> can help build a matching ruleset.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wait until <code>YOUR_DOMAIN<\/code> resolves to the VPS, then request a certificate and redirect HTTP to HTTPS:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo certbot --apache --redirect --agree-tos --no-eff-email -m YOUR_EMAIL -d YOUR_DOMAIN\nsudo certbot renew --dry-run<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Certbot should report a successful renewal simulation. It will also create the HTTPS Apache configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Complete the browser installer and schedule jobs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The browser wizard writes FileRun&#8217;s database settings and creates its first administrator account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open <code>https:\/\/YOUR_DOMAIN<\/code> and enter these values when prompted:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Database host: <code>localhost<\/code><\/li>\n\n\n<li>Database name: <code>filerun<\/code><\/li>\n\n\n<li>Database user: <code>filerun<\/code><\/li>\n\n\n<li>Database password: the value used for <code>YOUR_DB_PASSWORD<\/code><\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Create a unique administrator password. After signing in, open <strong>Control panel \u2192 Users<\/strong>, edit <code>superuser<\/code>, and set its home folder to <code>\/srv\/filerun-data<\/code>; the initial superuser does not have a home folder automatically. The <a href=\"https:\/\/docs.filerun.com\/install_on_php\" target=\"_blank\" rel=\"noopener\">official manual installation guide<\/a> explains why this folder must remain outside the public web root.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Now remove the database privileges and lock application files so PHP can change only runtime data:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb &lt;&lt;'SQL'\nREVOKE ALTER, DROP ON filerun.* FROM 'filerun'@'localhost';\nFLUSH PRIVILEGES;\nSQL\nsudo chown -R root:www-data \/var\/www\/filerun\nsudo find \/var\/www\/filerun -type d -exec chmod 0755 {} +\nsudo find \/var\/www\/filerun -type f -exec chmod 0644 {} +\nsudo chown -R www-data:www-data \/var\/www\/filerun\/system\/data\nsudo chmod -R u+rwX,g+rwX,o-rwx \/var\/www\/filerun\/system\/data<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">FileRun&#8217;s maintenance scripts clear sessions, classify new files, and clean old accounts. Run them from <code>\/etc\/cron.d<\/code> as the web account:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/cron.d\/filerun &gt;\/dev\/null &lt;&lt;'CRON'\n* * * * * www-data cd \/var\/www\/filerun &amp;&amp; \/usr\/bin\/php8.4 cron\/everyMinute.php &gt;\/dev\/null 2&gt;&amp;1\n*\/5 * * * * www-data cd \/var\/www\/filerun &amp;&amp; \/usr\/bin\/php8.4 cron\/every5minutes.php &gt;\/dev\/null 2&gt;&amp;1\n5 0 * * * www-data cd \/var\/www\/filerun &amp;&amp; \/usr\/bin\/php8.4 cron\/daily.php &gt;\/dev\/null 2&gt;&amp;1\nCRON\nsudo chmod 0644 \/etc\/cron.d\/filerun<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the FileRun installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run these checks to confirm the PHP extension, database, services, Apache syntax, and public HTTPS endpoint:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>php8.4 -m | grep -E 'curl|imagick|mbstring|pdo_mysql|xml|zip'\nphp8.4 -i | grep -i -m 1 ionCube\nmariadb -e \"SELECT VERSION();\"\nsudo apache2ctl configtest\nsudo systemctl is-active apache2 mariadb\ncurl -fsSI https:\/\/YOUR_DOMAIN | sed -n '1,5p'\nsudo -u www-data test -w \/srv\/filerun-data &amp;&amp; echo \"Data directory writable\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output includes the requested PHP modules, an ionCube line, a MariaDB 10.11-or-newer version, <code>Syntax OK<\/code>, two <code>active<\/code> lines, an HTTPS <code>200<\/code> or redirect response, and <code>Data directory writable<\/code>. Sign in, upload a small test file, refresh the page, and confirm it remains available.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Host FileRun Privately\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Debian VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Host FileRun Privately<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Deploy FileRun on a Debian VPS with root access, SSD storage, and a public IPv4 address.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-vps\" aria-label=\"View Linux VPS plans\">View Linux VPS plans<\/a>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><code>apt update<\/code> returns a Bullseye 404 or expired Release error<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Debian 11&#8217;s regular mirrors may no longer carry its old metadata. For an existing Bullseye server, change the main Debian entries to the archive and ignore the old validity date temporarily; schedule an upgrade to a supported release afterward.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo sed -i -E 's#https?:\/\/(deb|security)\\.debian\\.org\/debian#http:\/\/archive.debian.org\/debian#g' \/etc\/apt\/sources.list\nsudo sed -i '\/bullseye-security\/d' \/etc\/apt\/sources.list\nsudo apt -o Acquire::Check-Valid-Until=false update<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the failing entry is under <code>\/etc\/apt\/sources.list.d\/<\/code>, update or disable that specific Bullseye security entry too. Do not treat the archive as a permanent security feed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FileRun says \u201cionCube Loader is not installed\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Apache and the CLI can load different PHP configuration directories. Check both files, confirm the loader path exists, then restart Apache:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>test -f \/usr\/local\/ioncube\/ioncube_loader_lin_8.4.so &amp;&amp; echo \"Loader file exists\"\ngrep -R ioncube \/etc\/php\/8.4\/apache2\/conf.d \/etc\/php\/8.4\/cli\/conf.d\nsudo systemctl restart apache2<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On ARM64, the x86-64 archive is the wrong binary. Download the Linux ARM64 package from ionCube and install its PHP 8.4 loader instead.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The installer cannot connect to MariaDB<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The database name, user, password, or host does not match. Test the same account without exposing its password in the command line:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mariadb -u filerun -p -h localhost filerun -e 'SELECT 1;'\nsudo mariadb -e \"SELECT User,Host FROM mysql.user WHERE User='filerun';\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Enter the password when prompted. A successful connection prints <code>1<\/code>; use <code>localhost<\/code>, not a remote database hostname, in the FileRun wizard.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>403 Forbidden<\/code>, blank pages, or \u201csystem\/data is not writable\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Apache must be able to read the application and write only the runtime data directory. Reapply the ownership commands from Step 7, then inspect the error log:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R root:www-data \/var\/www\/filerun\nsudo chown -R www-data:www-data \/var\/www\/filerun\/system\/data\nsudo chmod -R u+rwX,g+rwX,o-rwx \/var\/www\/filerun\/system\/data\nsudo tail -n 30 \/var\/log\/apache2\/filerun_error.log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not use <code>chmod 777<\/code>; it grants every local account write access to the installation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Back up <code>\/var\/www\/filerun<\/code>, <code>\/srv\/filerun-data<\/code>, and the <code>filerun<\/code> database before updates or server changes.<\/li>\n\n\n<li>Keep the <code>system<\/code> directory blocked and test that <code>https:\/\/YOUR_DOMAIN\/system\/data\/<\/code> does not expose files.<\/li>\n\n\n<li>In <strong>Control panel \u2192 System \u2192 Update<\/strong>, review updates and temporarily grant the database account <code>ALTER<\/code> and <code>DROP<\/code> only when an update requires them, then revoke them again.<\/li>\n\n\n<li>Enable FileRun&#8217;s API only after HTTPS is working, and use a long, unique superuser password.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I install FileRun on Debian 11&#8217;s default PHP 7.4?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not with the current FileRun release. Current requirements use PHP 8.3, 8.4, or 8.5, so this guide installs PHP 8.4 from the signed PHP repository instead of using Bullseye&#8217;s PHP 7.4 packages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Where should FileRun store uploaded files?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use a directory outside Apache&#8217;s document root, such as <code>\/srv\/filerun-data<\/code>. This prevents direct URL access from bypassing FileRun&#8217;s sharing and permission checks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does FileRun need ionCube Loader?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">FileRun includes encoded PHP components that require ionCube to execute. The loader must match the installed PHP version and CPU architecture; a loader for PHP 8.3 or x86-64 cannot be substituted blindly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does FileRun store files in MariaDB?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. MariaDB stores accounts, settings, metadata, and sharing information. The actual documents remain in the filesystem directory assigned as each user&#8217;s home folder.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I install FileRun on Debian 11's default PHP 7.4?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not with the current FileRun release. Current requirements use PHP 8.3, 8.4, or 8.5, so this guide installs PHP 8.4 from the signed PHP repository instead of using Bullseye's PHP 7.4 packages.\"}}, {\"@type\": \"Question\", \"name\": \"Where should FileRun store uploaded files?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Use a directory outside Apache's document root, such as `\/srv\/filerun-data`. This prevents direct URL access from bypassing FileRun's sharing and permission checks.\"}}, {\"@type\": \"Question\", \"name\": \"Why does FileRun need ionCube Loader?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"FileRun includes encoded PHP components that require ionCube to execute. The loader must match the installed PHP version and CPU architecture; a loader for PHP 8.3 or x86-64 cannot be substituted blindly.\"}}, {\"@type\": \"Question\", \"name\": \"Does FileRun store files in MariaDB?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. MariaDB stores accounts, settings, metadata, and sharing information. The actual documents remain in the filesystem directory assigned as each user's home folder.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install FileRun with LAMP on Debian 11 using PHP 8.4, MariaDB 10.11, Apache, HTTPS, and secure storage paths, plus fixes for common install errors.","protected":false},"author":1,"featured_media":1142,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[5,9],"tags":[96,144,117,145],"class_list":["post-1141","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-debian-11","tag-filerun","tag-lamp-stack","tag-self-hosted-storage","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/comments?post=1141"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1141\/revisions"}],"predecessor-version":[{"id":4148,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1141\/revisions\/4148"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1142"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}