Admin Console problems

If Admin Console does not respond when you click tabs, commands, or options in the Admin Console, the Admin Server process might have stopped. You can restart the Admin Server process by using the fmsadmin RESTART ADMINSERVER command. For more information, see RESTART command.

The FileMaker Server service (Windows) or the fmserver_helperd daemon (OS X) starts and monitors the Admin Server process. By default, FileMaker Server will automatically restart the Admin Server process whenever it has stopped or is no longer responding for more than approximately one minute. If Admin Console restarts frequently, the cause may be that the time limit for Admin Console to respond is being exceeded in your deployment. You can prevent this behavior by turning off automatic monitoring with the fmsadmin AUTORESTART ADMINSERVER command. For more information, see AUTORESTART command.

• If the master machine has a firewall enabled, then you must open the ports required by FileMaker Server to communicate with users and administrators. See Ports used by FileMaker Server.

• If Admin Console doesn’t open, check whether the IP address of the master machine has changed. Each shortcut starts Admin Console for a specific FileMaker Server deployment. If the IP address of the master machine changes, you must remove the shortcut and start Admin Console from the FileMaker Server Admin Console Start Page again. See Starting Admin Console.

• If Admin Console is unable to connect to FileMaker Server, it is possible that the Admin Server process has stopped or FileMaker Server has only partially started. To check whether the Admin Server process has stopped, try using the fmsadmin LIST FILES command (see LIST command). If LIST FILES works, the Admin Server process has stopped and you can use the fmsadmin RESTART ADMINSERVER command to restart it. If LIST FILES does not work, use the Services control panel (Windows) or the launchctl command (OS X) to stop and restart FileMaker Server. For more information, see Starting or stopping the FileMaker Server service (Windows) or Starting or stopping FileMaker Server background processes (OS X).

This is normal behavior for the self-signed certificate that is included with FileMaker Server. Click the option to continue or go directly to the page.

FileMaker recommends that you request your own signed certificate from a certificate authority that matches your specific server name. For information on using the fmsadmin CERTIFICATE command to create a private key and Certificate Signing Request (CSR), see CERTIFICATE command.