Apple’s macOS Server 5.x has a rather different Apache configuration compared to the core macOS setup or those used in previous versions of Server. In particular, an instance of Apache is used as a proxy to any ‘backend’ copies of Apache. Here’s how to work around this…
Since FileMaker Server version 13, FMS has used its own Apache configuration files on macOS instead of just adding includes to the OS configuration files. Because of this, the technique I mentioned here no longer works for newer systems. This new arrangement has reduced issues for FileMaker Server’s web connectivity.
If you purchased your FileMaker Cloud server with user connection licenses, you may well wonder “Where do I get the client software to connect to my server?”.
A fair chance you’ll initially land on the screen below. This seems relevant, but there’s still no indication here how you can download the FileMaker Pro clients you have licenses for.
Here we’ll list the steps you’ll need to enable authentication using Amazon accounts with FileMaker Cloud.
If you’ll be having more than a few different people logging in to the Admin Console of your FileMaker Cloud server, it’s generally good practive to avoid having everyone use the same credentials. By enablling an additional authentication mechanism, you can easily add or remove administrative access to a server, and user’s get to use their own own credentials.
If you’ve installed the FileMaker Pro client using a “For Teams” license, or as part of your FileMaker Cloud server usage, you may see a new dialog in FileMaker Pro.
In version 15, FileMaker has introduced a a new user-based licensing model. With FileMaker for Teams and FileMaker Cloud, a license allows use of Server and Client software based on the number of subscribed users.
We’ll discuss how you can use a one or three year reserved instance for your FileMaker Cloud instance. This can shave 30% or more off your AWS instance charges.
When you spin up any new AWS based VM you will by default be using an hourly instance. This can be perfect for short-term usage or where your usage may fluctuate frequently.
If you had started a FileMaker Cloud deployment, but lost access, accidentally closed the page, or had some other issue that caused the process to stop, you may be able to restart your deployment easily by going to the AWS Marketplace and checking your history.