Thank you for your post.
It is not clear from your post what is happening when you try to access Admin Console.
First, launch a browser on the remote machine. Enter: http://<IP Address of server>
This should display:
If this displays, then you are able to remotely access the database server.
Assuming this does display, enter: https:<IP Address of server>:16000
Does this display the server with the option to start Admin Console? If not, then try port 16001.
Assuming you do get the option to start Admin Console, what occurs at that point?
TThanks. I am able to access the served files remotely. My url for addressing the admin console currently uses port 16001 and 16000 locally. I just can't access the console remotely. More in a moment . . .
Sorry. Just checked and it's the other way around. 16000 remotely and 16001 locally.
I'll do a port scan when back at the office. Obviously the ports needed to access the files are fine. If ports 16000 and 16001 have changed then we have a bug because these ports were open and certainly haven't been changed by me.
MY two cents . . .
Several reports of the FMS 14.0.4 update disabling the web server module have surfaced (me too) and this breaks the Admin Console when tried remotely. It's not port changes, it seems to be a bad bug.
time_saver and tcmeyers:
From the other links, there does appear to be an issue. In order to properly report this to Development and Testing, please let me know the SSL certificate being used.
Please let me know the machine and OS you are using.
This issue has also been reported at Re: FileMaker Pro 14.0.4 and FileMaker Server 14.0.4 updates now available and Update FMS 126.96.36.1992 Console and fmsadmin application problem? (in addition to those listed by tcmeyers.)
My environment: OS X 10.9.5 w/ the standard FMI SSL Cert (dev server)
Also, this page says Min. Requirement for #FileMaker Server 14.0.4 is El Capitan. Can that be correct??http://help.filemaker.com/app/answers/detail/a_id/5677
MacMini 8gigs ram with fast drive. OS X El Capitan. No SSL.
For some reason the forum make my replies as Correct Answer. Unmark as correct won't work.
The FMS machine had been running FMS Version 188.8.131.522 before attempting the update.
OS X Yosemite version 10.10.5 (14F1021)
Mac mini Server (Late 2012)
16 GB 1600 MHz DDR3
We don't use SSL for FMP client or FMGo client connections, all of these are in-house, so no custom certificate.
We use SSL for web access, but that is all via CWP/XML (not SSL), just the web server (not the FMS web server) can be accessed from the outside. The XML is pulled from the FMS web server/WPE by the actual web server NOT via SSL. The actual web server is another Mini running Apple's "Server" version 5.0.15 (15S4033). It uses only SSL to the outside world, with a custom certificate, but that is all presumably irrelevant to FMS.
In my case, immediately after updating, the XML access was killed, the "Web Server" Status in the Admin Console (as seen on the actual FMS machine) did NOT have the green check mark, and a few attempts at seeing what I could do with Terminal on the actual FMS machine it appeared that the command "fmsadmin" was unrecognized.
Normal operation under 14.0.3 was restored by saving the FMS settings/schedules, uninstalling FMS using the 14.0.1 full install/uninstall package, restarting, and reinstalling 14.0.1, and updating twice to get back to 14.0.3, and reloading the settings.
I actually tried updating to 14.0.4 again after all this, and failed the same way, so repeated all again but only as far is 14.0.3.
"The incorrectly drawn table"
I interpreted that only where an "asterisk" was placed beside the System requirements, then the version stated was the minimum requirement.
A few extra bits: It turns out fmsadmin was not running. I started it via Terminal. I did a port scan and port 16000 is NOT open. I can find no way to open it. This appears to be the problem.
Opening specific ports under Mac OS X 10.11 requires some Terminal commands, but it should not be needed.
Is port 16000 being used by another application? This would cause a conflict.
Assuming a firewall is active and turned on, temporarily turn it off so that all ports are available. Let's make sure you can access Admin Console.
If you want to open a specific port, there are several articles how to do this. Doing an internet search, I found:
Continue to keep me updated with any progress.