In a FileMaker Server deployment, the web server is the component that receives HTTP and HTTPS connections from browsers and web applications.
It provides the public entry point for services including:
- FileMaker WebDirect
- Custom Web Publishing
- FileMaker Data API
- FileMaker OData API
- FileMaker Server Admin Console
- Secure container data
- Other FileMaker HTTP services
Depending on the operating system and configuration, FileMaker Server uses Microsoft IIS, Apache, or Nginx.
What does the web server do?
The web server listens for incoming web requests, establishes secure HTTPS connections, and sends each request to the appropriate FileMaker Server component.
For example:
- A WebDirect request is routed toward the Web Publishing Engine.
- A Data API request is routed toward the Data API service.
- An OData request is routed toward the OData service.
- An Admin Console request is routed toward the administration service.
The web server does not host the FileMaker databases or interpret their layouts and scripts. Those responsibilities belong to the Database Server, Web Publishing Engine, FileMaker Script Engine, and other FileMaker components.
Microsoft IIS on Windows
On Windows, FileMaker Server uses Microsoft Internet Information Services, commonly known as IIS.
IIS is enabled and configured as part of the FileMaker Server installation when required. It handles HTTP and HTTPS communication for the FileMaker web services.
Recent versions can also use Nginx for HTTPS tunneling when that functionality is enabled.
Existing IIS websites may conflict with FileMaker Server because FileMaker normally requires ports 80 and 443. FileMaker Server should therefore be installed on a dedicated machine or in an environment where these ports are available.
Apache on macOS
On macOS, FileMaker Server uses its own instance of the Apache HTTP Server.
It does not rely on the general Apache installation that may be included with macOS. FileMaker manages the instance required for its services.
Administrators should avoid treating this instance like a conventional general-purpose website server. Manual configuration changes may be overwritten by FileMaker Server updates or interfere with the expected routing.
Nginx and Apache on Linux
Current FileMaker Server installations on Linux include both Nginx and Apache.
Nginx is the default web server, but the deployment can be switched to Apache when necessary.
This differs from the original CentOS-based FileMaker Server releases and has continued to evolve with the move toward Ubuntu.
Claris also provides tools for updating the FileMaker-managed Nginx and Apache components. Keeping these components current is important because the web server is directly exposed to network traffic and security vulnerabilities.
SSL certificates
The web server presents the SSL certificate used for HTTPS connections.
That certificate must be valid, unexpired, issued by a recognized authority, and match the hostname used to reach the server.
A valid certificate protects connections to WebDirect, APIs, Admin Console, OAuth authentication, and container data.
Certificate management is therefore not a cosmetic aspect of FileMaker Server. It is a fundamental part of the security and reliability of every web-based FileMaker service.
fmcloud.fm automatically deploys and renews valid SSL certificates for hosted FileMaker Servers.
Can the FileMaker web server host another website?
FileMaker Server includes a web root in which static files or Custom Web Publishing resources may be placed.
However, a production FileMaker Server should not generally be treated as a shared general-purpose website server. Additional applications, modules, configurations, and dependencies can create conflicts, complicate upgrades, and increase the security surface.
A separate web application can be hosted elsewhere and communicate securely with FileMaker through OData, the Data API, or Custom Web Publishing.
This separation is often easier to maintain and secure.
Web server, WPE, and Database Server
These components are related but not interchangeable:
- The web server handles HTTP and HTTPS connections.
- The Web Publishing Engine processes WebDirect and Custom Web Publishing sessions.
- The Database Server hosts FileMaker files and manages their data.
- The Data API Engine handles FileMaker Data API sessions.
- The OData service processes OData requests.
- The FileMaker Script Engine runs scheduled scripts, PSoS requests, and OData scripts.
A failure in one component may leave the others operational. For example, FileMaker Pro connections can continue working even when WebDirect is unavailable.
Web infrastructure expertise from fmcloud.fm
A secure FileMaker web deployment requires more than opening port 443.
The web server, DNS, SSL certificate, firewall, FileMaker connectors, WPE, APIs, and custom app must all be configured and monitored together.
At fmcloud.fm, this infrastructure is part of the managed hosting service. We automate SSL certificate management, monitor FileMaker services, and help diagnose problems across the complete path from the browser or API client to the hosted database.
