• Make sure TOTAL_UPLOAD_SIZE in config and PHP’s post_max_size / upload_max_filesize are all set high enough. For extremely large files, you might also need to increase max_execution_time in PHP or rely on the resumable upload feature in smaller chunks.

• FileRise itself doesn’t handle TLS. Run it behind a reverse proxy like Nginx, Caddy, or Apache with SSL, or use Docker with a companion like nginx-proxy or Caddy. Set SECURE="true" env var in Docker so FileRise knows to generate https links.

• Admin can change any user’s password via the UI (User Management section). If you lose admin access, you can edit the users/users.txt file on the server – passwords are hashed (bcrypt), but you can delete the admin line and then restart the app to trigger the setup flow again.

• In the uploads/ directory (or the path you set for UPLOAD_DIR). Within it, files are organized in the folder structure you see in the app. Deleted files move to uploads/trash/. Tag information is in metadata/file_metadata.json and trash metadata in metadata/trash.json, etc. Regular backups of these folders is recommended if the data is important.

-If using Docker, pull the new image and recreate the container. For manual installs, download the latest release and replace the files (preserve your config.php and the uploads/users/metadata folders). Clear your browser cache if you have issues after an update (in case CSS/JS changed).

For more Q&A or to ask for help, please check the Discussions or open an issue.