AnsweredAssumed Answered

CSS Images (Buttons/Colors) Break without Reverse DNS setup on IP address

Question asked by foxtailtech on May 19, 2015
Latest reply on Jul 7, 2015 by TSGal


CSS Images (Buttons/Colors) Break without Reverse DNS setup on IP address


FileMaker Server


Operating system version

Server 2012 R2, Server 2008 R2

Description of the issue

When Use SSL for Progressive Downloading is checked, AND  Reverse DNS isn't configured on the IP address of the server, FileMaker Server will use the server IP address, rather than the FQDN, to serve out CSS graphics (glyphs, colors). This of course causes an SSL validation issue with the browser and the graphic is not shown.

Steps to reproduce the problem

1.) Turn on SSL, and import your Cert.
2.) Check the box, Use SSL for Progressive Downloads
3.) restart database engine
4.) Clear browser cache or open an incognito browser window. (gets rid of cached images)
5.) open FMServer_Sample File in WebDirect in a browser

Expected result

Everything should come through using the FQDN typed into the browser and be encrypted via SSL.

Actual result

Glyph icons and color fills will not come through (images rendered by FileMaker CSS). You can turn on the browsers developer tools and look at network. You see that the connection is aborted do to SSL mismatch. CSS graphics are delivered over server IP address rather than FQDN.

Exact text of any error message(s) that appear

SEE Attached Image


I can either set reverse DNS to be the same as the FQDN of the server/SSL (IE SSL is registered to server1.domain.tld and reverse DNS is set to the same value) and edit the server deployment to remove web publishing, then edit it again and put it web publishing back in.

The other, is you can stop the FileMaker Server Process, edit the Server_Config.XML in the path of C:\Program Files\FileMaker\FileMaker Server\Admin\conf and replace the IP addresses with the FQDN. I believe updates and edit deployments will break this.

This issue exists in FileMaker 13 Server as well (but the Server_Config.xml is encoded in server 13).

A good number of ISP's will not allow rDNS to be setup.