[Stuart and Moscoe]

Do you have instructions for multi-server deployment with Filemaker Server 16?

According to FileMaker, PHP files should reside on the database server, not the web publishing engine server, as required under previous versions.

As a result, PHP file requests are forwarded using URL rewrite rules installed by the FileMaker server installer. However, the linked CSS and JavaScript files are not forwarded, which causes missing graphics and some functionality.

Do you know what URL Rewrite rules are needed to allow the linked CSS and JavaScript files to forward through to the Web Publishing Engine server?

[adminKeymaster]

FileMaker Server 16 now installs all Custom Web Publishing on the master machine. The worker machines are just for WebDirect.

However the worker machines will handle CWP requests by proxying them to the master machine, if you prefer to do that for security reasons. There doesn’t seem to be a reason to do this for performance reasons, as performance will be better by bypassing the proxy and just addressing the master machine directly.

To troubleshoot your set up, I would first make sure that soSIMPLE is working on the master machine. If it works on the master machine as expected, then check that the web ports for the proxy are set up correctly in your firewall.

[Stuart Mosscoe]

The network limitation prevents allowing access to the master machine directly from the internet.
The PHP pages and the calendar are working through the proxy installed by the FileMaker installer.
However, the CSS, Javascript, Fonts and supporting files linked to the PHP files, do not get proxied through the firewall to the worker machine.

A workaround according to FileMaker is to place that CSS and other files on the worker machine in the same relative location as the master machine. This works, but makes managing the site more difficult.

[Author]

Posts