5 posts in this topic
I have a setup with fms13 running on a network that is using an Airport Extreme as router, wifi and firewall. It has worked perfectly for years. However it started playing up recently so I tried to setup a new configuration for the Airport Extreme where I opened all the ports that I thought needed to be open for FMS13 to work : 80, 443, 5003, 389. What is weird is that if I install the new setup in the Airport Extreme web direct does not work. I know that it actually functioning in FMS as I can test it locally. If I install the old setup in the Airport Extreme web direct does work, however after a few minutes the Airport Extreme becomes inaccessible, and I fear unreliable, as you can see in the attached image. Would someone know what I am missing here?
We have a newly deployed OS X 10.10.5 Server with FMS14 installed with only 3 databases hosted, all accessible via Web Direct.
Now some of our customers are experiencing difficulties with even accessing our solutions, which we have narrowed down to local network problems at our customers.
The problem is, the login window is not showing, and therefore they can't access the databases.
I then tried to connect to the database through Chrome, which worked perfectly fine!
Is there something I can do for the customer or on our Server, to prevent this message for future customers?
I am using FM Server 15 on MacOS (10.11.15), and trying to get SuperContainer to work with Web Direct clients. I am having several issues using the Web Direct clients, so I hope someone can help me.
1. First of all, which installation option do I use?
I am referring to the SC Documentation http://docs.360works.com/index.php/SuperContainer#Option_1:_Using_SuperContainer_as_a_standalone_server_application:
Option 1: Using SuperContainer as a standalone server application
Option 2: Installing SuperContainer with FileMaker Server
In both scenarios, I can see FM Server being depicted. What are the pros and cons of using each one?
2. Which http port to use?
Option 1: port 8020?
Option 2: port 80? Do I specify port 80 when I run SuperContainerServer.jar? I get the error message "Could not start/stop SuperContainerProtocol handler initialization failed: java.net.BindException: Permission denied:80." What is the reason for this? Is it because I am using the trial version?
I followed the instructions for Option 2. I am unable to use the Mac installer in the SuperContainer zip file. The installation hangs: "Installing latest 360Works Admin application. Installing 360Works Tomcat daemon...". Then I tried to follow the manual installation instructions. I copied the SuperContainer folder into: /Library/FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/ . Then I added 2 lines into the mod_proxy.conf file in /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/:
ProxyPass /SuperContainer http://127.0.0.1:16020/SuperContainer
ProxyPassReverse /SuperContainer http://127.0.0.1:16020/SuperContainer
According to the documentation, this is supposed to "modify the tomcat configuration files to serve SuperContainer content on port 80". Are the steps correct? According to the documentation, adding these two lines is supposed to Modify the tomcat configuration files to serve SuperContainer content on port 80?
The reason I need help to check with the installation is because I am having issues using SCSetBaseURL and SCGetInfo on my web clients. (I did copy the SC companion plug-in into /Library/FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins.) Thanks in advance for some guidance!