![]() ![]() This port is used by Admin Console and for web publishing (HTTPS) if SSL connections are used. The secure web connections port, port 443.This port is used by Admin Console and for web publishing (HTTP). In the server computer's firewall, open the necessary ports so that FileMaker Server can communicate with administrators and clients: The installer creates a separate web server instance and enables it for FileMaker Server to use on these ports. If it is enabled, ensure that no existing website uses port 80 or 443. macOS: The web server included in macOS does not need to be enabled.Windows: The FileMaker Server installer enables the IIS web server if it isn’t already enabled, then runs the Microsoft Application Request Routing (ARR) installer, creates its own website in IIS, and configures the website to use the ports specified for web connections.If the FileMaker Server installer detects existing websites using these ports, you must disable those websites and make the ports available. These ports are used by FileMaker Server even if web publishing is disabled. FileMaker Server requires that port 80 is available for web connections and port 443 is available for secure web connections. The web server serves web publishing clients, hosts the web-based Admin Console application, and handles some data transfer tasks. To install on more than one machine, see Deploying FileMaker Server across multiple machines.įileMaker Server requires a web server in all deployments. See Creating a certificate signing request.This section explains how to install FileMaker Server on a single machine. Trusted connections require a custom SSL certificate installed to digitally identify your server. 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. Request your own signed certificate from a certificate authority that matches your specific server name. Click the option to continue or go directly to the page. This usually occurs for systems that don't have a custom SSL certificate installed. See Starting or stopping the FileMaker Server service (FileMaker Server only, Windows), Starting or stopping FileMaker Server background processes (FileMaker Server only, macOS), or Starting or stopping FileMaker Server background processes (Linux).īefore the Admin Console Sign In page appears, your web browser displays a security message If the list files command does not work, use the Services control panel (FileMaker Server only, Windows) or the launchctl command (FileMaker Server only, macOS) to stop and restart FileMaker Server. If the list files command works, the Admin Server process has stopped and you can use the fmsadmin restart adminserver command to restart it. To check whether the Admin Server process has stopped, try using the fmsadmin list files command (see CLI help for the list command). 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. If the IP address of the primary machine changes, you must remove the shortcut and start Admin Console from the Sign In page again. Each shortcut starts Admin Console for a specific FileMaker Server deployment. If Admin Console doesn't open, check whether the IP address of the primary machine has changed. If the primary machine has a firewall enabled, then you must open the ports required by FileMaker Server to communicate with users and administrators. Cannot start Admin Console from a remote machine You can restart the Admin Server process by using the fmsadmin restart adminserver command. If Admin Console does not respond when you click tabs, commands, or options in Admin Console, the Admin Server process might have stopped. Admin Console problems Admin Console does not respond
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |