CentOS FMS on FMP Client Machine

Using VirtualBox - Data directory on host nfs-share

Install your "portable" FileMaker Server on your developer machine in a lightweight VM, keep Data on your filesystem.
Or install FMS19 additional to your locally installed FMS16/17/18 (macOS)

nfs Share on macOS:

create folder fmsdata in /Users/Shared/
add it to nfs-exports:

$ sudo pico /etc/exports

add line:

/System/Volumes/Data/Users/Shared/fmsdata -mapall=root localhost

to access the nfs share via localhost (nat to VM):

$ sudo pico /etc/nfs.conf

add line:

nfs.server.mount.require_resv_port = 0

grant Full Disk Access to nfsd:
System Preferences —> Security & Privacy —> Privacy —> Full Disk Access —> cmd + shift + G —> /sbin/nfsd —> Enter

restart nfs deamon:

$ sudo nfsd restart

read more here:

nfs Share on Windows:

for this to work on "non Server" Windows (10), you need to install a nfs server

C:\Program Files\nfsd\nfsctl.exe —> Edit —> Preferences —> Exports —> Edit exports file
(also accessible through Control Panel —> haneWIN NFS Server)

add line:

C:\fmsdata -name:fmsdata -mapall:{win user sid}:S-1-5-114 -range 

(get your users SID in cmd: wmic useraccount where name='username' get sid)

Windows —> Start —> haneWIN Software —> start NFS Server

copy the FMS Installer and maybe needed selfsigning Root certificate to …/fmsdata/Install/

Blog about selfsigning Root-cert:

for „green locks“, add a /etc/hosts entry pointing to the fqdn of your FMS (as in certificate)
or if you run your internal dns, add a CNAME pointing your FMSs fqdn to your host machine

Install VM

min. 3 GB Ram (for WebD), ~8 GB disk (VDI dynamic)
Networkadapter: NAT
Port redirections (examples):
• FMP 50030 5003
•  SSH 2022 22
•  WebD 8443 443
•  fmsadmin 16005 16000

Default IPs on VBox (Adapter 1):
• VM:
• Host:

Install CentOS 7.9 minimal

in install dialog:
• activate network set hostname (with nat network adapter just leave the ip as is, check the assigned ip, else set fixed ip)
• set root password
• add —> advanced add group membership wheel

login via ssh (macOS terminal / windows puTTY):

$ ssh -p 2022 {user}@

$ sudo yum install nfs-utils nfs-utils-lib

$ sudo yum install nano

check if you can see nfs shares:

$ showmount -e

create mountpoint:

$ sudo mkdir /media/fmsdata

add share to fstab:

$ sudo nano /etc/fstab

add line:

(macOS host) /media/fmsdata nfs rw,sync,hard,intr 0 0

(windows host) /media/fmsdata nfs rw,sync,hard,intr 0 0

add FMS dependency:

$ sudo yum install centos-release-scl
$ sudo reboot

login via ssh (macOS terminal / windows puTTY):

$ ssh -p 2022 {user}@

check if nfs mounts are present

$ cd /media/fmsdata

$ ls

$ cd Install

create folders for fms/Data:

$ sudo mkdir -p /opt/FileMaker/FileMaker\ Server

link /media/fmsdata as Data to FMS install directory:

$ sudo ln -s /media/fmsdata /opt/FileMaker/FileMaker\ Server/Data

install fms:

$ sudo yum install filemaker_server-19.2.1-23.x86_64.rpm

go through the installer, set fmsuser a.s.o

if needed add self issued Root certificat from the share:

$ sudo cp YourRootCert.cer /etc/pki/ca-trust/source/anchors/

$ sudo update-ca-trust extract

$ sudo service fmshelper start

login via browser:

import certificate

import license

set server name to fqdn

stop database server

$ sudo service fmshelper stop
$ sudo service fmshelper start

your FMS is up. The system uses about 3.5 GB of data, I assigned 8GB.

In FMP add host: your.fms.box:50030

Access WebD: https://your.fms.box:8443/fmi/webd

With ssl port forwarding, upload filemaker file to host from FMP does not work. But as the Data-directory resides in the hosts filesystem, just copy it to macOS: /Users/Shared/fmsdata/Databases/ windows: C:\fmsdata\Databases

I’ve tested this on windows and it seems to work, but I’m not sure about performance and reliability, test thoroughly first. Otherwise it might be better to keep the files inside the VM. 

Currently there are no comments, so be the first!