Removing port 80 and 443 conflict with macOS Server 5

Apple’s Server 5.x has a rather different Apache configuration compared to the core Mac OS 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.

Unfortunately, this setup has the proxy always listening (attached) to ports 80 & 443, even if the sites in Server GUI are disabled and the Web service is off. This is problematic if you want setup something outside of Server (e.g., FileMaker Server) that needs to attach to ports 80 or 443.

One option to avoid this conflict is to modify the proxy configuration to no longer listen on these ports. The configuration file for this can be found at:

/Library/Server/Web/Config/Proxy/apache_serviceproxy.conf

Once you have the file open in an editor, make the following changes.

For each of these directives using port 443 or 80:

  • use 9443 instead of 443
  • use 8080 instead of 80

Directives that need to be changed are:

  • Listen
  • VirtualHost
  • RequestHeader

I’ve done this often enough that I’ve finally come up with a full sed based shell script to make these changes:

A possible problem with this approach is that either later Server upgrades might blow out these changes, or the Server upgrade may stumble due to the non-standard configuration.

Another option may be to disable the proxy from starting in the first place. However, I haven’t yet tracked down what is instantiating this process, as it doesn’t use the more typical methods of doing this on Mac OS.

If you see a lot of messages like the ones below in your system.log, your changes either got overwritten or have errors:

Simon

Debug Apache on a FileMaker Server

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.

Continue reading “Debug Apache on a FileMaker Server”

FileMaker Client installers with FileMaker Cloud

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.

Continue reading “FileMaker Client installers with FileMaker Cloud”

Use Amazon OpenID authentication with FileMaker Cloud

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.

Continue reading “Use Amazon OpenID authentication with FileMaker Cloud”

What’s this "Sign in to FileMaker Server" dialog?

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.

Continue reading “What’s this "Sign in to FileMaker Server" dialog?”

Using an AWS Reserved Instance with FileMaker Cloud

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.

Determine Usage

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.

Continue reading “Using an AWS Reserved Instance with FileMaker Cloud”

Restart interrupted FileMaker Cloud deployment

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.

Continue reading “Restart interrupted FileMaker Cloud deployment”

Step-by-step for FileMaker Cloud

Although setting up your AWS account and creating a new FileMaker Cloud instance is a fairly easy process, it does have dozens of steps, and a few places where you could easily take a wrong turn. On this post we’ll go through each step in the configuration of your Amazon AWS account and requesting your first server.
Continue reading “Step-by-step for FileMaker Cloud”

Version 0.84 of bBox for FileMaker Now Available

Optimized for FileMaker 15, the new version of bBox includes 160 examples

We are pleased to release another update to bBox, v0.84 of our free utility plug-in to extend FileMaker solutions to other programs, code libraries, and OS X functions including Python, Ruby, AppleScript, Perl, Bash/sh, XPath, and SQLite.

Continue reading “Version 0.84 of bBox for FileMaker Now Available”

1 2 3 6