2 Replies Latest reply on Aug 9, 2017 7:22 AM by mark.stuller

    SSL update broke our server..?

    mark.stuller

      Hello

       

      We needed to update the SSL certificates (expiring) today and so shutdown our servers (5 FMS15), installed the certificates and restarted the servers. All came back up as expected except one server, our only split-deployment install.

       

      That server came back w/ the database server fine, new certificate and all. But the worker machine did not.

       

      So our Operations staff called FileMaker tech support and was told to 're-install' (yeah, I know SOP). That did not resolve the issue.

       

      We are able to connect to the worker machine w/ a browser to confirm that the FMS Apache is running and has the certificate installed, but a webdirect database as well as MirrorSync cannot connect to the worker machine. The FMSAdmin Console reports that the Web Publishing engine is running.

       

      So there is a open ticket w/ tech support but I'm hoping others in the community can give us things to look for/try while FM works their open ticket.

       

      OS: 10.12.6

      FMS: 15.0.3.308

       

      Thank you for your thoughts.

        • 1. Re: SSL update broke our server..?
          wimdecorte

          mark.stuller wrote:

           

          We are able to connect to the worker machine w/ a browser to confirm that the FMS Apache is running and has the certificate installed, but a webdirect database as well as MirrorSync cannot connect to the worker machine.

           

          What specific error?

           

          And if you turn SSL off on both master and worker temporarily, does it then work?

          • 2. Re: SSL update broke our server..?
            mark.stuller

            Hello

             

            Thanks Wim.

             

            We did find the solution. When *initially* creating a split deployment server a specific port (which port my memory fails me) is used to communicate between the Master and Worker machines. We had this port blocked at the firewall since we had previously setup the Master/Worker servers.

             

            Thanks for reading! Mark

            1 of 1 people found this helpful