Once you have FileRun running, it is strongly recommended following these steps in order to secure it:
.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.
.php files are not accessible via the web server./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.
superuser, is the only account not
protected against brute force login attacks, so it is very important
that you set a password that cannot be guessed by a computer. Set a
long password, containing also uppercase letters, digits and symbols.session.cookie_httponly is set to On, in your server's
PHP configuration file, for increased security against
cross-site-scripting attacks. Update the configured MySQL user
account and remove the ALTER and DROP privileges.system/data folder and its contents, where FileRun needs to be able
to make changes.display_errors is set to Off, in your server's PHP
configuration file.When using Docker, use only an official FileRun Docker image.