Network Considerations
This page details the ports, protocols and firewall rules needed to ensure connectivity between the Devin App, Devin Engine, and all Devin Server environments.
Devin App ↔ Devin Server (Development)
First, make sure your Development Server can talk to your computer—because the Devin App on your PC only ever connects to the Devin Engine on that server. In practice, this means allowing your computer’s IP address through the server’s firewall (so it can accept your incoming connection).
Default FileMaker Server Requirements
Both ports 443 and 5003 are part of a default FileMaker Server installation. If you’re already hosting files through FileMaker Server, they’re almost certainly open and configured correctly—no extra network changes should be required to connect your Devin App and Devin Engine.
HTTPS
443
FileMaker Server API access
FMNET
5003
FileMaker Pro access to hosted fmp12 files (Devin Engine)
Devin Server ↔ Devin Server Routing
All traffic to Staging or Production environments is routed through your Dev Server— the Devin App never connects to them directly. On the Dev Server, the Devin Engine and Devin Server API communicate locally over HTTP on localhost:45712 (configured automatically at install). When the Dev Server reaches out to another Devin Server, it uses HTTPS (default port 443) through the same Apache or Nginx web server that FileMaker Server uses for Admin Console, WebDirect, and Data/OData APIs, leveraging your existing SSL certificate and reverse-proxy settings for end-to-end encryption — just like accessing the FileMaker Admin Console in a browser.
Environment-Specific Requirements
Internet-Exposed
Allow HTTPS on TCP/443
Accept HTTPS on TCP/443 only from Dev Server's IP
Internal (LAN/VPN)
Allow HTTPS on TCP/443
Permit HTTPS on TCP/443 per ACL
Last updated
Was this helpful?