![]() ![]() ![]() To sum up, our syntax is (for a server with an IP address of 192,168.1.1 - a wild card such as 192. The FileMaker Server Admin console application before version 13 uses Java Webstart. The wildcards either side changed the behaviour so that we can only access the admin console from within the server, external access via port 443 (or any port via the firewall) is now disabled and WebDirect works. Some of our customers are still on FileMaker Server 12 for some reasons. We replaced "admin-console" with "*admin-console*" The Filemaker Admin API application is a FileMaker solution designed to run using FileMaker Pro Advanced software to administer a FileMaker Server that. We pasted our revised syntax just above (formatting added below otherwise the syntax isn’t displayed) : ![]() Open this in Notepad run as Administrator, otherwise changes cannot be saved To add a bit more detailed information, the configuration file that has to be changed is at:Ĭ:\Program Files\FileMaker\FileMaker Server\HTTPServer\conf We only require the admin console to be available on the server FMS is running on).Īfter much testing the best we achieved was to have the admin console unavailable along with WebDirect unavailable. (192.168.1.1 entered as an example server IP address. I’ve found that the published didn’t work: There may be times when your server’s FMSE will freeze up and your schedules will fail to run, even though they appear to be running when looking at them in the FileMaker Server Admin Console (Configuration > Script Schedules). I’ve just secured 4 Windows servers on the cloud that, as a result of this FMS 19.4.1 update, have had their admin console publicly available on the Internet for the first time in over 10-years. aACE’s automation schedules are run by the FileMaker Script Engine (FMSE). See Creating a certificate signing request.As with all IT information, there is an assumption of too much knowledge within these instructions. ![]() 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. Before the Admin Console Sign In page appears, your web browser displays a security message See Starting or stopping the FileMaker Server service (Windows) or Starting or stopping FileMaker Server background processes (macOS). 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. 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).
0 Comments
Leave a Reply. |