# Getting Started

# Installation

FileMage is exclusively distributed through the major cloud provider marketplaces as a virtual machine image. To start using the application, you must first have an account with the cloud provider of your choice, and then deploy our virtual image into your account using the marketplace.

For detailed instructions on how to deploy the application from one of the cloud provider marketplaces, see these instructions:

# First Time Access

After deploying the virtual machine make note of its IP address. The web portal will be available at https://<server-ip>/. A self-signed certificate is used, which you will have to accept to bypass the browser warning. See Encryption and Certificates for instructions on how to install a signed certificate.

When logging in to the web portal for the first time, you must prove your ownership of the virtual machine by connecting as a system administrator user. From there you will be able to create your initial application administrator account. Once you have created an account, refresh this page to login to the application web portal.

# Windows

filemage init
  • Enter a email address for the administrator account.
  • Enter a password for the administrator account.
  • Refresh the page, or click Done.

# Linux

sudo filemage init
  • Enter a email address for the administrator account.
  • Enter a password for the administrator account.
  • Refresh the page, or click Done.

Note

The filemage init command can be run non-interactively in automation scripts using flags. See Command Line Interface

# Default Ports

By default, the following ports are used. See Configuration Reference for information on how to change these ports.

Description Windows Linux
HTTP 80 80
HTTPS 443 443
SFTP 22 2222
FTP 21 21
FTP Passive 32768-60999 32768-60999

Note

When HTTPS is enabled traffic on the HTTP port will be redirected to the HTTPS port.

Note

To use SFTP in Linux on port 22 sshd must be reconfigured to use a different port.

Restrict Administrative Ports

It is strongly recommended that you restrict access to the web portal (80, 443) and SSH (22) to trusted IP ranges.