I have also had this problem, although I am not using the Web server. I found that when I re-boot the computer the correct IP address is displayed. It does not fix the problem for good as it will return at a later time, usually after uploading new or revised files to the server.
Unfortunately rebooting doesn't fix mine.
Thanks a lot for your answer. I appreciate.
Your case and mine are similar.
After 3 deployments, I have the same result.
Of course, if I have the solution, I'll tell you.
Can you ping that 88 address? Is it a live address on your network?
Does FMS have multiple network cards? (Ether + WiFi)
Thanks for the inquiry!!
Please also see screen shot where I have definitely configured for single computer deployment.
Please also see screen shot where only 1 network connection, (although it does have Wifi & a 2nd network port on the computer).
If I ping the network, no other device is using 192.168.1.88 so it comes back with unable to reach host.
It is interesting to not that at some point someone turned on Wifi (which did have the 192.168.1.88) address.
But after disabling wifi, restarting computer, redeploying filemaker server web component, it still thinks the web is on IP 192.168.1.88.
Here's hoping someone can provide an answer short or wiping the computer.
Here's what I would do:
- set FMS to not auto-host files
- disable all but one network adapter (don't make it Wifi)
- assign that one network adapter a static IP address
- reboot the machine
- run the FMS deployment wizard again (available from the admin console)
Yes I've done all those things, and that's my standard procedure and I still have the problem.
I think when their internal guy tinkered and turned on wifi, it somehow picked up that IP, saved it back somewhere in Apache and now I can't get it to pick back up the computer's actual IP address. I think the problem is somewhere in Apache, although it was running 14.02 server and the problem was reversed, the webserver was corrected, but filemaker's web companion had the wrong IP address. So I updated to 14.04, redeployed web and it seemed to move the problem from web publishing engine to the web server. I'm thinking FM server wrote something to apache and that's what needs to be undone.
So I was doing some playing around and ran across this tech article.
So I ran sudo apachectl graceful to shut down apache.
Then I restarted apache with.
sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist
Now I've made a little headway because.
http://192.168.1.100, Now loads the default apache site (when before it wouldn't).
And http://localhost also loads apache.
Now when I try to edit filemaker deployment, filemaker still gives me an error (404), but it no longer shows the web server with the wrong IP address, it actually doesn't show the webserver at all on the status screen Now I may have completely fubar'd things, but hey apache is running again now, so that's a step in the right direction.
Also the web publishing engine will now turn on, but I can't actually load any of the web direct databases, but before I couldn't toggle it on.
Now I'm going to see if a restart will get filemaker server to connect to it, but I can do that until after business hours.
I'm having this exact problem with FMS 188.8.131.522 on a Windows Server 2012 single-machine installation.
multiple NICs in that machine? All set to static IP?
Two NICs, but only one connected. It's set to static IP. The web server shows a different IP.
I sort of solved it via Admin Console -> Server -> Edit Deployment. The correct IP now shows up, but Admin Console shows Web Server as down:
IIS says FMWebSite is running (I restarted it a couple time), and the "FileMaker Database Server Website" page loads fine on http://192.168.1.54, so I guess it's okay. Bugs me that Admin Console shows it as down, but it seems to work. A server restart didn't have any effect.
Just did a full uninstall & reinstall. I think it may be related to two different versions of Application Request Routing, as specified here:
There's apparently one version for FMS 14v3 and earlier, and another for 14v4 and later.
Hopefully this will save someone else from burning a full day's productivity trying to figure it out.
So I was reading somewhere that installing the updates doesn't get you the same installation as installing with filemaker 14.04 server.
So at the time I only had the updaters, but somewhere along the line I got a copy of the fms_14.04 installer. I'm an FBA member, so when I sell software to clients I get a copy of their order. So somewhere along the line I got the full 14.04 installer, not sure what someone else would do, probably ask their sales rep to regenerate their install keys for them so they could pull down the full installer.
Anyway, I backed up my settings, uninstalled and reinstalled with the 14.04 installer and every things fine.
Two interesting side notes for people.
1) When I reinstalled 14.04 it said their were websites running would I like to disable them, but the funny thing is, the computer was bought specifically for filemaker server and no other installs, configurations etc., so I have to believe that is some remnant of web direct from 14.02 filemaker. Anyway I said yes disable and then all was good.
2) I have another client that has a backup server. Since they are using an external thunderbolt raid, they wanted a cloned exact duplicate computer so that in case of computer hardware failure they could just swap over the raid to the 2nd box power it up and be online. So we did a test of doing that emergency fail over and when I did that the web component on the secondary computer would not come online it said there was another webserver on using the current IP and indicated the name of basically the primary computer (i.e. also the secondary computer because it's an exact clone using carbon copy cloner). So I ran the 14.04b update and it fixed the webserver problem. Then when we switched back to the primary computer same problem again ran the 14.04b update and problem fixed. Then we wanted to try it a second time and same problem and this time we uninstalled the 14.04b update and webserver fixed.
Hope this helps someone else!!