Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About tcfitzgerald

  • Rank

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
    Windows 10

Recent Profile Visitors

2,086 profile views
  1. I know this post is a few months old, but I was curious if you ever got any where with this. We recently installed FileMaker Server 16 and are having the same issue.... We are running Windows Server 2008 R2 SP1. What OS are you running?
  2. So, just an update on this... We did end up purchasing third-party SSL certs and they work fine. However, about two weeks ago, InCommon added the Comodo Elite SSL to the list of certs we could request. I just tested it out and it worked fine. Unlink most of the other certs issued by InCommon, the certificate authority in root path is actually Comodo NOT InCommon.
  3. Yes, you can just delete the serverCustom.pem, and restart the FM services. That will remove it from use on the database server, but not the web server. You will have to manually adjust the Apache settings for that (probably adjust the http.conf that WebDirect is using, it may have also copied the cert somewhere specific for Apache). Having never used FileMaker server on a Mac, i'm not sure what the official recommendations are for that. Also, namecheap resells several of the supported certs: https://www.namecheap.com/security/ssl-certificates/domain-validation.aspx I use the $39 thawte
  4. I've tested FMPA 13.v05 against server 14 with a 3rd-party SSL cert installed and it works fine. I think the compatibility issues are mostly the other way around. Newer clients with older servers mixed in with using the default SSL cert.
  5. Wim, I'd love for it to be that easy, however; they look at that list and say, 'InCommon certs are just Comodo certs so it should work fine'.
  6. James: Thanks for the input! I'd love to just purchase one of the supported certs, but I think I'm going to need to prove that the InCommon cert just won't work before they let me do that... It works fine with the default FileMaker supplied cert with SSL on, so I don't think it's a firewall issue. Using SSL on the server doesn't change the port being used to communicate between the server and clients, it all goes over 5003, SSL or not (at least this is what running package capturing software has indicated, as well as the FileMaker documentation). I find it odd as well that I don't get an
  7. Thanks! I watched the video and the only difference I can see in my steps is that the FileMaker Server name under "General Settings" was not set to the FQDN of the server. I updated it to match but it didn't help. I'm going to try and get a trial / free SSL cert from one of the supported vendors and go from there...
  8. We are working through the steps to bring all of our FileMaker 13 servers to 13.0v9 but are running into a bit of trouble with the custom SSL part. A little background: • We have a process for requesting and obtaining SSL certificates through InCommon (https://www.incommon.org/certificates). This is our IT Security Office’s preferred way to obtain SSL certificates • Technically, Comodo issues the certs, but Comodo is nowhere to be found in the Certification Path of the certs we get from InCommon (they are issued by InCommon RSA Server CA) • InCommon is not one of the vendors listed
  9. I was not able to resolve the issue without doing a complete uninstall and reinstall. If this is a fresh install, did you apply any updates after the initial install? Is this a two-machine configuration? If it is a two-machine config, and any of the updates apply to the web publishing engine / web server you want to make sure to apply those updates first, and then update the Master database machine. If you do it backwards, you will run into some of the symptoms you describe.
  10. I do not see any log messages that indicate the Web Publishing Engine has crashed/stopped. From the last time I restarted the Master machine: 2014-12-10 07:38:13.110 -0600 Information 488 Stopping FileMaker Server... 2014-12-10 07:38:13.110 -0600 Information 410 Stopping FileMaker Database Engine... 2014-12-10 07:38:16.573 -0600 Information 412 FileMaker Database Engine stopped. 2014-12-10 07:38:16.573 -0600 Information 490 FileMaker Server stopped. 2014-12-10 07:38:23.219 -0600 Information 745
  11. Wim, Thanks for the reply. I should have mentioned that I have tried this several times but it does not help.
  12. This past Monday I pulled up the Admin console for one of our new FileMaker 13 servers and noticed that the status indicator next to “Web Server” was greyed out and it was reporting that XML was disabled. It also reported that the Web Publishing Engine was not running and FileMaker WebDirect was disabled.  When I checked all of these services, they were running just fine. I was able to connect to WebDirect and our CWP pages were working. I've tried restarting both servers, but nothing changed. I can also change all of these settings in the Admin console (e.g. disable XML, stop
  13. The Enterprise Services Application Development group at the University of Iowa is looking for a web application and database solutions developer with some FileMaker expertise. The ideal candidate will have experience with PHP web development as well as FileMaker development. Many of our PHP applications are built with FileMaker as the backend. Some of the tools we use to accomplish this are the CodeIgniter PHP framework and FX.php. We also administer FileMaker Server for hosted campus solutions, so experience with FM Server is a plus. Those with experience in other languages or genera
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.