Troubleshooting > Admin Console problems
 

Admin Console problems

Admin Console does not respond

If Admin Console does not respond when you click tabs, commands, or options in Admin Console, the Admin Server process might have stopped. You can restart the Admin Server process by using the fmsadmin restart adminserver command. See CLI help for the restart command.

Cannot start Admin Console from a remote machine

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 Sign In 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 CLI help for the list command). If the list files command works, the Admin Server process has stopped and you can use the fmsadmin restart adminserver command to restart it. If the list files command does not work, use the Services control panel (Windows) or the launchctl command (macOS) to stop and restart FileMaker Server. See Starting or stopping the FileMaker Server service (Windows) or Starting or stopping FileMaker Server background processes (macOS).

Before the Admin Console Sign In page appears, your web browser displays a security message

This usually occurs for systems that don’t have a custom SSL certificate installed. Click the option to continue or go directly to the page.

Request your own signed certificate from a certificate authority that matches your specific server name. If you use the standard FileMaker Server certificate, users may be warned of a problem with the website’s security certificate because the standard certificate doesn’t verify the server name. Trusted connections require a custom SSL certificate installed to digitally identify your server.

See Creating a certificate signing request.