I am responsible for a solution hosted by FMS13 running on a mac mini server, located remotely in a place that I get to physically only once a week or less. Users mostly access files using FMGo, either in the same physical location as the server over wifi, or remotely using cellular data. As the router connects to the internet over cable, it has a dynamic IP.
I would like to be able to test whether fms13 is actually serving filemaker files, on a regular basis, so I can an early warning if something is not working. As things stand, we now have a situation where a user attempts to connect using FMGo, and if they are unsuccessful, they text me or email me to try and fix the problem. This is disruptive to my schedule and also seriously hampers the user's work.
I'm using site24x7.com to monitor the status of several websites that I am also responsible for, and this has shown itself to be very helpful. I would like to use the same service, and presumably could if FMS13 also served a file over the web. Unfortunately, that seems to be impossible as long as I'm running os x server yosemite on the mac mini. If I turn off os x server (by dragging it to the trash) then I can turn on FMS web serving, but I lose the ability to make changes to open directory users and groups. Apparently, according to filemaker support, the inability of FMS to do web serving when os x server is running is because FMS does not work well with os x versions more recent than mountain lion.
It would be possible, I think, to set up a script to run periodically on a remote machine to ssh in to the mac mini and verify the status of FMS using the command line interface, but since this requires usernames and passwords, it's not something I would want to farm out to a third party like site24x7.
Is there a way to check the availability of files using fmnet which will not require a filemaker client, and could be run by a service such as site24x7?