I have Server 13 running successfully. I can access databases remotely using Go/Pro, but when I enter the ip address in a browser to use Web Direct, I get nothing, just a blank page. What am I doing wrong?
No, everything goes through the web server (IIS / Apache), the web server redirects to FMS.
make sure to use a url like this:
http://<your web server>/fmi/webd
Make sure you also have Sharing turned on proper for Web Direct (under file menu).
I'm using a url like that, also web direct sharing is on, and the server admin console shows that it's on, but still nothing...
And just to confirm, the part above that contains <your web server> is the ip address, correct?
Like this right? (screenshot from FMS admin console)
Wimdecorte helped me out through a private message. Thank you! Turns out that my router was not setup to forward ports 443 and 80 to my server box. I don't know about anyone else, but it's not clear to me that is part of the FMS setup. I guess that is what my original post was trying to ask. Hope this post helps anyone else struggling with this.
I would like some more detail about this.
Do I understand correctly that FileMaker with Web Direct requires a dedicated machine that CANNOT be using Apache's default web service for web sites on ports 80 and 443? In the Mac OS-X server, it is not possible to point the default web service to any ports other than 80 and 443, although Apple says that you could possible hack Apache to accomplish that.
So my question is, if I have no access to a router which is directing calls to the server, is there a way to keep Web Direct focused on ports other than 80 and 443, so that the Mac OS-X Web Service can also be turned on?
FM is the webserver itself so it would not effect another webserver as long as FM was assigned a different port (like 8080).
Im still a little new and might be missing something, but with my testing this is what im seeing. What it looks like is that FM13 runs a little heavy and you may want to run it on its own hardware with no other services running (depending on its use)
I understand that FM13 with Web Direct can require a lot of RAM and I am prepared for that with 16GB and an SSD drive for speed. However, I am caught in the middle of conflicting tech support directives.
Apple says that the ports for the Web Sites "service" in OS-X Server cannot be modified. I'm perfectly willing to assign FM-WD to different ports, but I don't see where or how to do that. FM tech support says that Web Direct requires a "dedicated machine" which translates to having a second server on another hardware device that handles web calls, pointing to the data source on the first server. That could mean I have to uninstall and redeploy as a 2-machine deployment, I suppose, or it could just be a web server elsewhere without FM installed. Not sure.
For now, I am able to view Web Direct on the server itself, but unable to see it from elsewhere. FM tech support tells me I need to adjust the port forwarding on my router. Huh? If the OS-X web service is turned off and FileMaker is listening on ports 80 and 443, why is port forwarding necessary when I'm not using a domain name, just the machine's IP address. I confess, I don't get it.
Im running FM 12 - but i bet its the same
--> its under sharing - IWP (Webdirect) - advanced settings.
"The TCP/IP address in the Instant Web Publishing dialog box determines where web browsers can find FileMaker Pro databases on the host computer. By default, FileMaker files are shared from port 80. If port 80 is already in use (by a web server or another application), consider changing TCP/IP Port Number to 591. FileMaker, Inc. has registered port number 591 with the Internet Assigned Numbers Authority (IANA) specifically for web publishing."
dburnham wrote: For now, I am able to view Web Direct on the server itself
For now, I am able to view Web Direct on the server itself
If you can see it in a browser on the server itself but not from another machine then it would point to a firewall issue.
Port forwarding only comes into play when you traverse networks. For instance when you want to access that server from outside your network. As long as you stay within your own LAN, no port forwarding is needed. But if the server runs a firewall then you need to open up the necessary ports on that firewall.
I had a similar problem with a clean install on a Mic Mini running OS 10.7. There were no warnings or irregularities when I installed FMS13 (I only used default settings), Mac web services were running fine (I could get to the demo 'Welcome to Server' page), and FMS reported that WebDirect was enabled and that the database was shared over WebD.
Only I got an apache error every time I tried to open http://<myserver>/fmi/WebD.
I tried various combinations, including localhost and 127.0.0.1 from the server itself, but no luck. The fact that the 'Welcome to Server' was hosted showed that it wasn't a DNS or firewall/router issue.
In the end I completely uninstalled FMS13 and re-installed it. During installation a dialgue box popped up saying something like "the defaul website is blocked" and would I like to unblock it. I clicked 'yes', and the rest of the installation/deployment continued without incident. After that WebDirect was working without problems.
I guess this means that it's a permissions error somewhere?Jon.
I got the same message during the deployment, even though the Mac OS-X Web Service is off. It could be because I have an FTP Server running - but I doubt that because the FTP Server is using ports 8080, 9090, and 4443. So there should be no confilct.
Regarding Jonathan's post, I was under the impression that FMS-13 is not certified to run on 10.7. It requires 10.8 or 10.9. On 10.8, you can run OS-X server, but on 10.9 the Server is not yet officially blessed.
Also, my inability to reach the server from outside the LAN is not relevant because the firewall is turned off.
I don't know if it is related, but I have two other issues: Plugins are recognized but will not enabled. I click the button, a message appears in HTML-5 saying the plug in is enabled, but the checkbox does not stay checked and the plug-in is not enabled.
Also, FWIW, I can log in to the Admin Console with my user name and password. I can change the user name and password any time i want. But no matter what I do the FMP client cannot upload a database without getting the message "invalid username or password"
Jonathan Jeffery wrote: Only I got an apache error every time I tried to open http://<myserver>/fmi/WebD.
Jonathan Jeffery wrote:
I wonder if you have more than one version of apache running? or something? For example, when I install MAMP for testing purposes, it installs a complete set of files needed to run. The "A" is for apache, of course. But it's only "on" when I run MAMP and tell it to turn on. However, if I enable "Web Sharing" through System Preferences, it calls a separate location on my computer. I never have both running at the same time.
> Try HTTPS
Yes, I did. As with http, the 'Welcome to Server' page was available, but not WebDirect.
• Did search for 'Apache'?
• Or see what "web" processes are running?
• What is your web server setup?
• Are you serving other web pages (besides WD)?
• If you are getting the welcome (apache), then what is the URL to display it?
• Use the IP of the machine if you are testing same machine, rather than 'localhost' or even '127.0.0.1'.
• If coming from another machine, use the IP rather than the domain name, if any.
• Force the port with:
• Do you have any directory defaults changed? These typically list index.htm, index.html & perhaps index.php or default.htm or other default pages that should be served. The order determines what is first choice. So if you have .htm before .php and BOTH files are in the server directory, the first one is the default. Sometimes this is the only problem and you can re-arrange the defaults order or create redirects within the pages to force from one to the other.
See what results you get.
-- sent from my iPhone4 --
Thanks, Beverly. I hope this reply is 'on-message' because I don't have these things fully digested yet.
First, I have verified that only one version of Apache is running. My understanding is that even though the installation of FMS turns off the OS-X Server's "switch" for the Web Sites service, it does not disable Apache. I could be mistaken about this but in my machine right now, Web Direct is working, and the Server's app reports Web Sites as "off".
In the Apple OS-X Server, you cannot modify the ports (80 and 443) used by the Default Web Site. Similarly, FileMaker Server 13 does not allow you to assign the Web Direct Service to ports other than 80 and 443, the way we used to be able to do with port 591 for IWP. It seems to me that the way FileMaker has designed FMS-WB to install is to deny the user the ability to modify a configuration that they know will work. Maybe this is an effort to minimize support issues during this first release of Web Direct and it will change in the future? Just a hunch.
One thing I've learned about the Apple OS is that when you have OS-X Server installed, the Web Sharing item in the Sharing pane of System Preferences is disabled, and replaced by the Web Sites service of the Server app. This is important to know even if FileMaker is not involved, because the location of your web site directories is not in Library/Web Server/Documents/...., but instead in Library/Server/Web/Data/Sites/
I've recently done a complete reinstall of FMServer 13. In the course of doing this, I discovered that my FTP Server (Crush 6) was using port 9090, which happens to be one of the ports used by FileMaker Server. As a result, any attempt to upload a database into the server resulted in an error message "Invalid Username/Password" which was puzzling since I was able to log into the Admin Console without a problem. Changing the Crush port to 9191 fixed that. FYI there is a knowledge-base article #12120 that gives a list of all the ports required by FMS 13
FileMaker tells me that it's not possible to run CWP solutions on the same CPU as Web Direct. They say that FMS13 with Web Direct requires a "dedicated machine" that is not hosting any other web sites. I've not seen this written/published anywhere, but it's what they say over the phone. To be fair, I was also told that FMS-13 is not certified for Mountain Lion Server, only for the regular version of Mountain Lion, but that is contradicted by the published Tech Specs for FileMaker Server under OS-X 10.8, albeit it's true for Mavericks 10.9.
When I run the FMS Test page and click the link for testing Web Direct, I get an index page with a circular graphic with a large capital-T. Probably represents "Test". .... or maybe Texas, with Devcon coming to San Antonio? :-)
So it seems to me that this index page, which resides in the directory shown below in this screen shot, tells us where the root of the web server is when FileMaker Web Direct has taken over the machine's web services.
This is confirmed by taking the URL of the Web Direct test page, and replacing the machine's internal domain name with the IP address of the server, and accessing the same index page from another computer on another network. That works,
So it seems to me that these directories "htdocs" or httpsRoot" could be the place to locate CWP solutions. I have not tried it yet because I am weary of uninstalling and reinstalling FMS. Perhaps FMS can't resolve domain names, but that can be done within the OS-X Server's DNS Service. Therefore, I don't see why it wouldn't work when the URL begins with the server's IP address.
Which takes me back to the original question about port forwarding. Why would anyone need to play with their router to forward ports, and if so, which ports and where would you forward them? That's the part that makes no sense to me because it looks to be unnecesary.
Thanks for trying!
Retrieving data ...