If you are currently running FileMaker Pro or FileMaker Pro Advanced on the same machine, quit before installing FileMaker Server.To upgrade from an earlier version of FileMaker Server, see Upgrading or moving an existing installation.Port 16002 must be open on the master machine, open in the firewall, and available on the worker machines.Port 16000 for server administrators using Admin Console.This port is used by Admin Console and for web publishing (HTTPS) if SSL connections are used. The secure web connections port, port 443.This port is used by Admin Console and for web publishing (HTTP). In the server computer's firewall, open the necessary ports so that FileMaker Server can communicate with administrators and clients: The installer creates a separate web server instance and enables it for FileMaker Server to use on these ports. If it is enabled, ensure that no existing website uses port 80 or 443. macOS: The web server included in macOS does not need to be enabled.Windows: The FileMaker Server installer enables the IIS web server if it isn’t already enabled, then runs the Microsoft Application Request Routing (ARR) installer, creates its own website in IIS, and configures the website to use the ports specified for web connections.
If the FileMaker Server installer detects existing websites using these ports, you must disable those websites and make the ports available. These ports are used by FileMaker Server even if web publishing is disabled. FileMaker Server requires that port 80 is available for web connections and port 443 is available for secure web connections. The web server serves web publishing clients, hosts the web-based Admin Console application, and handles some data transfer tasks. To install on more than one machine, see Deploying FileMaker Server across multiple machines.įileMaker Server requires a web server in all deployments. This section explains how to install FileMaker Server on a single machine.