FileMaker Server: port 443
- Darrin Southern
- 2 days ago
- 3 min read
Updated: 1 minute ago
For want of a better blog title, this blog post details the issues and solutions we've experienced as part of an update for a client who is updating their FileMaker Server, so we've taken this opportunity to configure a number of external services . . .
On Premise Server.
This client is unique in this 'day and age' - as the FileMaker Servers are housed on premise - bare metal with ups etc - within the client's head office location.
That said, today's FileMaker Server is an active citizen in this world's connected Servers.
FileMaker Upgrade.
As part of the long overdue upgrade from FileMaker Server 19 to FileMaker Server 21, these 'core' internal and external services are required
FileMaker Pro
FileMaker WebDirect
FileMaker Pro.
Local (AU) and international (NZ) access requires 'traditional' port 5003 via the internal network and also via the 25+ OpenVPN connections.
WebDirect.
Along with the Claris FileMaker Server native FileMaker Pro clients, there is a need for public WebDirect access, for 50+ staff to enter their timesheets.
External Services.
As part of 'future proofing' their servers with this update, we're also setting up a FileMaker 22 Server, with these native and external services
FileMaker Pro
FileMaker WebDirect
Claris Studio
Claris Connect
Claris MCP Server
OttoMatic and OttoFMS
Claris Studio.
A further uniqueness of this client is that head office is in Australia. Currently there are no Claris Studio or Claris Connect Servers in our region.
These are the current Claris Studio regions
US West (us-west-2)
Europe - Frankfurt (eu-central-1)
Asia Pacific - Tokyo (ap-northeast-1)
While these are actually AWS sites, there is currently no way to set your preferred region or to see any latency reporting - I've asked Claris to add this to the product . . .
Port 443.
All these external services connect via port 443.
This includes the FileMaker Server Admin Console and the OttoFMS Admin Console.
It's worth noting that the FileMaker Server Admin Console was via port 16000 and is now via port 443
OData.
FileMaker Server will require OData to be enabled for Claris Studio, along with the required permissions via the Extended Privileges.
DataAPI.
FileMaker Server will require DataAPI to be enabled for Claris Connect, along with the required permissions via the Extended Privileges.
Current Configuration.
The 'Network Guy' had configured the FMS19 on 443, and the FMS21 on 4431.
This created issues that the SSL Certificates would not be correctly configured, and WebDirect was reporting regular 'Connection Errors'.
nginx
This is where we have installed nginx (Engine X) on the network. Along with defining which external ports are forwarded to which internal servers and ports, the SSL Certificates for each server is also configured.
It's worth noting that nginx is also one of the local functions within FileMaker Server 21 Web Publishing for WebDirect for 'load balancing'.
Network Errors.
Initial configuration attempts returned a number of generic 'network errors' which led to a number of key areas of troubleshooting on these issues
Host Unreachable
Ports Closed
SSL Certificate incomplete
Platform not supported
Postman.
The primary tool I consistently use to verify access to online ports and services is Postman.
Viewing the anticipated data outside of FileMaker facilitates basic troubleshooting.
The second advantage is the ability to share these Environments and Collections with non-FileMaker developments for API calls, among other uses.
ToolKit.
For each of the issues below, I've added a link to an online tool
Host Unreachable.
Due to this Server being on premise, then there's a need to ensure the DNS and/or firewall is configured to allow access from the required regions around the world. The 'check host' site allows checking regions and/or accessible via port 80.
It was also necessary to eliminate the 'blanket' geo-blocking implemented by the Network Guy, which was done without informing us and was preventing our connections from the US.
Ports Closed.
Although port 80 can be a simple test, we're focusing on port 443 for this external access and/or services. There are various 'port checker' sites - just ensure that these are hosted in the same region as the Server as Service (SAS) resides.
SSL Certificate incomplete.
Configuration on the Firewall and FileMaker Server, the 'intermediate' must to be configured correctly - without the intermediate, certain services fail or report errors.
Platform not supported.
In this case, the Claris Studio Data Sources from FileMaker Server require is FileMaker 22.
Summary.
The final outcome is that we have a successful site setup to allow the client to expand their on premise FileMaker Server solution - for the 'foreseeable' future . . .