Providing the above runs without any error messages This may be due to us not including the speech marks to begin with. Note - we seemed to have a problem using paste in the command line, the above failed until we typed it in rather than copying and pasting from our notes. In the command line enter (substituting your own certificate name):įmsadmin CERTIFICATE IMPORT "C:\Program Files\FileMaker\FileMaker Server\CStore\myserver_craftict_co_uk.crt" To: C:\Program Files\FileMaker\FileMaker Server\CStore\ Open Notepad on the server and paste the certificate contentsĮnsure 'Save as type:' is set to 'All Files' Upon receipt of the email containing the SSL certificate or a link to the certificateĬopy all contents including and between '-BEGIN CERTIFICATE-' and '-END CERTIFICATE-' The application will include an email to the person who must approve the request for the domain before the certificate can be issued. Use the contents of your clipboard to paste into the online certificate signing request (CSR) and follow through the website until you receive your certificate by email for the FQDN you've requested.ĭuring the process you will have to enter the appropriate company and personal details for the domain. Go to your chosen certificate issuer's website Select all, copy contents, close and use below Open serverRequest.pem with Notepad (created by the above) Navigate to C:\Program Files\FileMaker\FileMaker Server\CStore\ In the command line for the details listed above enter:įmsadmin CERTIFICATE CREATE "/CN=.uk/O=Craft ICT Ltd/C=GB/ST=Mystate/L=Mytown" In both cases # in front of any entry will disable it (sound familiar?)Īs a precaution, use of the command line below was run with elevated permissions by right clicking and selecting 'Run as Administrator' Add the required lines, use ctrl O and Enter/Return to save and then ctrl X to close - theĝNS cache can be cleared by using 'dscacheutil -flushcache' Open Terminal, enter 'sudo pico /private/etc/hosts' and enter your computer password. Open Notepad using 'Run as Administrator' (this will not work if you right click on the hosts file and open Notepad), File:Open, ensure 'All Files' is selected, navigate to C:\Windows\System32\drivers\etc\hosts and enter the appropriate lines as above, then save and close - the DNS cache can by cleared by using 'ipconfig /flushdns' in the command line or just restart the computer When you go live, you can remove these host file entries. If we are deploying 2 servers for FileMaker (master) and WebDirect (worker), we'd also add a line for the worker computer on both servers (and any computer you're connecting to these). Therefore, assuming our server address is 1.12.123.4, we would enter into the host file: To overcome this while configuring a replacement server, or if the server's DNS entry hasn't been setup, we recommend editing the host file on the new server and any computer you're using to configure this. Connecting to the same server using will not display a certificate error. Connecting to will display a certificate error. This is a particular problem if the server being configured is to replace a server still in use using the FQDN, therefore our new .uk server cannot be accessed via this name (say, for example a new FileMaker Server 14 is replacing an existing FileMaker Server 13).Įven more obvious is if you connect to the FileMaker admin console via a web browser.
Filemaker server 13 setup pro#
For instance you can follow the procedures below, try to upload your first database using FileMaker Pro File:Sharing menu and receive a message such as: However, it is not quite as straight forward as that. Access to the FileMaker Server via an IP address will result in the grey padlock, not the green. If 'Use SSL for database connections' is selected, any access to the server after the certificate has been installed must be via the FQDN for the green padlock to appear in FileMaker Pro. If you've already set the server name in the FileMaker Server admin Console, this can be changed after the SSL certificate has been installed if necessary. Your server must be named in the FileMaker Server admin console (General Settings, Server Information tab, Server Name) as per the fully qualified domain name (FQDN) used on the SSL certificate in this case as above '.uk' For the example below we are using a server name of:
Please substitute any of the above with your own details when referenced below.īefore starting any work on with FileMaker Server, we strongly suggest you make some DNS preparations. The procedures below assume we are setting up a server as follows: Server name: We hope it will short circuit for others much of the investigations and testing we carried out.įor additional information setting up a 2-server deployment see below The following was documented during our initial FileMaker Server 14 setup.
Filemaker server 13 setup windows#
E: > FileMaker Server 14 SSL Certificate Setup For Windows ServerįileMaker Server 14 SSL Certificate Setup For Windows 2012 Server
0 kommentar(er)
