I understand only 80 and 443 can now be used for the server installation. Is this confirmed? If that is the case that is very unfortunate as I have web server on the same network (but different machine)

Yes.....

Same problem.

 

 

 

Edited June 11, 20187 yr by D4V1D

The custom ports in v16 work just fine. I wonder why the option was removed?

I have been having major problems after installing FMS 17 and the new MirrorSync.  First, it said web server was not running.  After hours of searching, I found that I needed to forward port 42424.  Now I need to reconfigure the Mirrorsync configuration file.  I have the IP's set as different and they are correct but MirrorSync is saying that the MirrorSync server at the IP address is not accessible on port 80.  I had this same problem with FMS16 and I got around it by selecting port 8080.  Now, we can't do that!!!  

How am I supposed to get MirrorSync running like this?

I'm having this same issue. Dead in the water right now.

I figured out a way to get custom ports in FileMaker Server 17 so that it can coexist with macOS server 5.6.1 inside macOS High Sierra 10.13.6:

Install macOS High Sierra + all updates.

Then, install macOS server

Finally, install FileMaker Server 17.

If you get the "Apache is running" error, try to install again while running this terminal script (See https://community.filemaker.com/thread/156699 )

while sleep 5; do sudo killall -9 httpd; done  

After installation, control C the script to stop it.

 

Then, after installation, you can change the ports that FileMaker Server is using by making 3 edits in two files:

   in  /Library/FileMaker Server/HTTPServer/conf/httpd.conf  change "Listen 80" to "Listen XXXX" (one place)
   in  /Library/FileMaker Server/HTTPServer/conf/extra/httpd-ssl.conf  change 443 to YYY (in two separate lines)

(this assumes you want ports XXXX for HTTP and port YYYY for HTTPS)

In theory, you should be able to restart FileMaker's apache process by :

sudo fmsadmin restart httpserver

But I found it didn't "take", however rebooting the entire sever seems to have fixed it.

I now have a server running macOS High Sierra 10.13.6, with FileMaker Server 17.0.2, and macOS Server app 5.6.1 all running happily together.

 

Note that macOS Server 5 does some weird things with port-mapping and proxies for services such as CalDAV which really want to run on 80 and 443. 

I found it much easier to change FileMaker's ports, rather than trying to change macOS server's ports.

I hope this info can help others.

 

 

Edited August 25, 20187 yr by xochi
clarity

Interesting - so this survives a computer reboot?

19 minutes ago, Aussie John said:

Interesting - so this survives a computer reboot?

Yes, in fact I couldn't get it working until I rebooted.

I suspect that it might not survive a software update to FileMaker server, if those two files get edited during the upgrade.

 

Thanks for the tip, xochi.

I found that without changing FMS's https port number it is impossible to access WebDirect from behind the router running NAT. Even if there's nothing else running on the machine hosting FMS, you can't specify port forwarding like port 5000 on external IP -> port 443 on internal FMS IP. They must be the same number otherwise there's going to be a blank page with a cross at the top left corner if accessed from the internet. And in my case those standard ports are already taken by a web server running on another machine.

Edited October 26, 20187 yr by Buckie

I found this was also true with FileMaker Server 14 - you really need to run WebDirect on its own static IP address on the normal HTTPS port 443.    

If you don't, weird things can happen - although it may work with some clients, there may be issues for some companies that are running SSL proxy firewalls.

Thanks that works and easy to redo as it survives reboots but not updates, as I found out this morning.

Cheers,

Steve.