I've had the same issue. I've got FMS13 installed on Mavericks Servier in Parallels, on my MacBook Pro. I can access the admin console inside the virutual machine, but not outside of it.
I've had similar issues with Admin Console's prior to version 13. Would not connect from the remote machine using the latest version of Safari, but does connect using Chrome.
Same problem here with FMS 13 on Mountain Lion Server. Guess we now know it's not unique to us individually...
I ran into the same problem, but realized later that I wasn't using the https protocol.
So make sure to conect remotely using something like this:
Hope this helps.
I got this method to work in Chrome. Chrome told me that the certificate wasn't trusted. I proceeded anyway and it worked. Oddly on port 16000. I thought FMS13 went to 16001.
And it worked in Safari as well. Same thing - certificate is not valid.
Tried with Safari, Firefox and Chrome here. HTTP and HTTPS. Nothing works.
Looks like WebDirect doesn't either, either locally or remotely, but FileMaker Network Sharing does.
I show OS X's firewall as off.
Also, using the hostname for the machine locally on the server also doesn't work to access the admin console, only "localhost" does. Oy.
Yeah, it is odd. And the error that you get when you try to hit it remotely (without https / port 16000) is obscure...
From the FMS Getting Started docs: "Note that Admin Console always uses an HTTPS connection on port 16000 from remote machines. You can also use http://[host]/admin-console, which works because it is automatically redirected to HTTPS on port 16000."
However, I don't see the automatic redirect working.
Flattening the machine and starting again. Mainly as it became apparent that adding Server in to the mix wasn't a help.
Will try Chrome &/or https once it's back in about 30 minutes . . .
And just in case anyone has lost the will to live with the lack of an idiot's guide, the web direct url is http://[host]/fmi/webd/
This will sound lame. but try restarting the server, and then look in the logs to see what IPs FMS is listening on. It sounds like it is only listening on 127.0.0.1.
Good idea, but nope, logs show it listening on both 127.0.0.1 and the external IP address.
It was worth a try I guess.
In my case, I'm using Safari 6.0.5, and connecting remotely to FMS 13 running on OSX 10.9 (without OSX Server).
I connect with this: https://10.0.1.100:16000
I do get a certificate warning. If I then select "Continue" I get the admin console.
OK, got it all working after a server restart. There's definitely screwy stuff going on with the http/https/16000/16001 redirects, but I eventually found the right combination.
We wouldn't love FileMaker so much if they handed it to us on a plate - I know they know we love a challenge!
So, re-installed and . . .
http://ip.addr.goes.here:16001 as implied by the deployment wizard yields can't connect message
As does https
http://ip.addr.goes.here/ brings up a shiney logo - ooo, shiney.
HTTP Status 404 - /error/HTTP_BAD_REQUEST.html.var
FileMaker Server has encountered an error:
The requested resource is not available.
If the Server Launch Page is not available, visit the FileMaker Website for more assistance.
which is not inspiring at all!
However, https://ip.addr.goes.here:16000 - and the crowd goes wild
I'm sure it's buried somewhere in the documentation. However, I don't have the time to read everything that every release comes with produces, getting the Cliff notes on day 1 will always endear me to a particular vendor. Hint hint!