Jump to content

tcfitzgerald

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tcfitzgerald

  • Rank
    member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,123 profile views
  1. FMS 13 Custom SSL woes

    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.
  2. 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 SSL123 on my personal dev server and it works fine.
  3. FMS 14 with FMP 13 clients?

    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.
  4. FMS 13 Custom SSL woes

    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'.
  5. FMS 13 Custom SSL woes

    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 error when trying to list the databases. I do get an error on the first screen (Connection Failed) if I try to upload a database. Gary: A bit confused by your replies...are you saying your InCommon cert worked at first but is no longer working? At any rate, I was able to get the free trial Quick SSL Premium cert from Geotrust (listed as supported) to work on my personal dev server. Next step will be to get the same cert for our test/dev server at work and go from there...
  6. FMS 13 Custom SSL woes

    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...
  7. 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 here http://help.filemaker.com/app/answers/detail/a_id/11413 Our IT Security Office and Windows Server Admins asked that we try the InCommon certificates to see if they work. I generated the certificate request using the “fmsadmin certificate create” command and gave the CSR to our Windows server admins to request an SSL cert. I am able to import one of the certs using the “fmsadmin certificate import” command, however; after I do this no FileMaker clients are able to connect to the server. CWP and WebDirect are not able to connect to the databases. When I use “Open Remote” to try and view the databases on this server I am not able to see any databases. The Admin console works fine and reports that all of the databases are “Normal”. I’m not seeing any errors in any of the logs. I’ve restarted the servers, and have restarted the database server /services several times with no change. If I turn off SSL, or remove the serverCustom.pem file everything starts working again. This is a two machine configuration running Windows 2008 R2 Enterprise SP1 currently running 13.0v5. I’m using FileMaker Pro Advanced 13.0v5. The certificate is SHA-2, but according to FileMaker that shouldn’t be an issue with the versions I’m running. Are the symptoms I’m seeing a result of the certificate not being one of the support vendors / types? Could I have done something wrong in generating the CSR? Am I importing the wrong certificate? Here are the options for types of certs I can download: PKCS#7 Base64 encoded PKCS#7 Bin encoded X509, Base64 encoded X509 Certificate only, Base64 encoded X509 Intermediates/root only, Base64 encoded X509 Intermediates/root only Reverse, Base64 encoded The only one I could actually import was the X509 Certificate only, Base64 encoded cert, all of the rest gave this error: fmsadmin: This certificate [server.cer] does not match the key file [E:\Program Files\FileMaker\FileMaker Server\CStore\serverKey.pem] I did notice that the Subject of the resulting certificate does not match the Subject info I supplied when generating the CSR. It seems the Windows Server Admin who actually did the cert request put in some default values for their group. Any insight would be helpful and will hopefully help me convince our IT Security Office and Windows Server admins that we actually need to purchase one of the supported SSL certs from FileMaker's list. Thanks!
  8. FMS 13 Admin console unable to get status of WPE / CWP

    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.
  9. FMS 13 Admin console unable to get status of WPE / CWP

    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 Stopping FileMaker Server processes... 2014-12-10 07:38:23.235 -0600 Information 704 Stopping FileMaker Script Engine process... 2014-12-10 07:38:23.235 -0600 Information 952 FileMaker Script Engine process stopped. 2014-12-10 07:38:23.235 -0600 Information 704 Stopping Progressive Backup process... 2014-12-10 07:38:29.350 -0600 Information 952 Progressive Backup process stopped. 2014-12-10 07:38:29.584 -0600 Information 704 Stopping Admin Server process... 2014-12-10 07:38:35.169 -0600 Information 952 Admin Server process stopped. 2014-12-10 07:38:35.169 -0600 Information 704 Stopping HTTP Server process... 2014-12-10 07:38:35.231 -0600 Information 952 HTTP Server process stopped. 2014-12-10 07:38:35.231 -0600 Information 746 FileMaker Server processes stopped. 2014-12-10 07:41:52.691 -0600 Information 743 Starting FileMaker Server processes... 2014-12-10 07:41:52.691 -0600 Information 703 Starting HTTP Server process... 2014-12-10 07:41:52.722 -0600 Information 703 Starting Progressive Backup process... 2014-12-10 07:41:52.753 -0600 Information 703 Starting Database Server process... 2014-12-10 07:41:52.784 -0600 Information 703 Starting Admin Server process... 2014-12-10 07:41:53.814 -0600 Information 703 Starting FileMaker Script Engine process... 2014-12-10 07:41:53.814 -0600 Information 162 Starting FileMaker Server 13.0v5 x64 (11-06-2014)... 2014-12-10 07:41:53.830 -0600 Information 763 Running on Windows Server 2008 R2 Enterprise x64 (6.1.7601, Service Pack 1), with 24 logical processor core(s) And the worker: 2014-12-10 07:36:07.548 -0600 Information 704 Stopping FileMaker Script Engine process... 2014-12-10 07:36:07.548 -0600 Information 952 FileMaker Script Engine process stopped. 2014-12-10 07:36:07.673 -0600 Information 704 Stopping Java Web Publishing Engine process... 2014-12-10 07:36:13.336 -0600 Information 952 Java Web Publishing Engine process stopped. 2014-12-10 07:36:13.336 -0600 Information 704 Stopping Web Publishing Engine process... 2014-12-10 07:36:17.392 -0600 Information 952 Web Publishing Engine process stopped. 2014-12-10 07:36:17.485 -0600 Information 704 Stopping Admin Server process... 2014-12-10 07:36:19.638 -0600 Information 952 Admin Server process stopped. 2014-12-10 07:36:19.638 -0600 Information 704 Stopping HTTP Server process... 2014-12-10 07:36:19.685 -0600 Information 952 HTTP Server process stopped. 2014-12-10 07:36:19.685 -0600 Information 746 FileMaker Server processes stopped. 2014-12-10 07:36:24.100 -0600 Information 743 Starting FileMaker Server processes... 2014-12-10 07:36:24.100 -0600 Information 703 Starting HTTP Server process... 2014-12-10 07:36:24.147 -0600 Information 703 Starting Admin Server process... 2014-12-10 07:36:26.315 -0600 Information 703 Starting Web Publishing Engine process... 2014-12-10 07:36:26.378 -0600 Information 703 Starting Java Web Publishing Engine process... 2014-12-10 07:36:27.579 -0600 Information 744 FileMaker Server processes started.
  10. FMS 13 Admin console unable to get status of WPE / CWP

    Wim, Thanks for the reply. I should have mentioned that I have tried this several times but it does not help.
  11. 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 the WPE) and they keep working.  I’ve tried running the Deployment Assistant on the master machine but it gets stuck at the part where I’m supposed to specify the IP of the Web Server. I put in the IP address, but the master machine says that the IP address is “not found”. I can ping the worker from the master machine, I can run PortQry (http://support.microsoft.com/KB/310099 ) and it reports that the master machine can contact the worker on ports 16000, 16001, 80, and 443.  This was all showing fine in the Admin console on Sunday (or at least I don't remember seeing any issues).  This is a two machine config running Windows 2008 R2 with FileMaker server 13.0.5.520.  Here is a screenshot of what I see:   You might notice how it says the WPE is off and XML is disabled but that there is 1 CWP connection (you can ignore that PHP is disabled, that is actually true...)
  12. 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 general database development with a desire to work in PHP and FileMaker are encouraged to apply. You can view the full job posting here: https://jobs.uiowa.edu/pands/view/64991
×

Important Information

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