5 Replies Latest reply on Jun 8, 2017 2:12 PM by Michael Frankel

    FMS 16 Web Direct over EC2 - can't connect

    Michael Frankel

      HI -


      I'm running Web Direct on an Amazon EC2 instance The instance is running Windows Server 2016.


      Before I get into my questions, let me get the essential things out of the way:


      1. All required ports are open via EC2 (Security Group) and the Windows Firewall is turned off.
      2. I am able to access the database using FileMaker Remote.
      3. I can access the database via WebDirect if I'm RDP'd into the machine on AWS.
      4. The machine has an Elastic IP (i.e., it's static).


      So now let me tell you the issue. I cannot connect to the database via WebDirect from my office computer. I can see the list of databases in the main WebDirect screen, host-ip-address/fmi/webd, but once I click on one, nothing happens.


      When it does fail, what I see is that the beginning of the URL has switched from the public IP to the private IP of the server. That leads me to my next questions:


      1. Do I need to change the "network" on the server to "public"?
      2. How do I get WebDirect to only use the public IP?
      3. When I go into the Admin Console, it shows the private, not the public IP. Is that the problem? If so, how do I fix it.


      Any help on this would be much appreciated.




      Michael Frankel

      Wizard Consulting Group, Inc.

        • 1. Re: FMS 16 Web Direct over EC2 - can't connect

          Hi Michael,

          what happens if you ignore the elastic IP entirely and just use the Public DNS or IP that was assigned by AWS?

          EG: ec2-YOUR_IP_ADDRESS.compute-1.amazonaws.com


          You can find the public IP assigned by AWs under the EC2 Control Panel > Instances page > Select Instance > "Description" tab.


          I'm not sure, but I don't think Elastic IPs are meant to work with FMS on AWS.


          If you try and hit the public DNS above with /fmi/webd on the end, does everything work as expected?


          Also, did you make sure to allow ports 80 and 443 through the inbound rules for your AWS/EC2 security group? It sounds like port 5003 is working fine on that.

          • 2. Re: FMS 16 Web Direct over EC2 - can't connect
            Michael Frankel

            Hi Mike -


            I tried what you suggested before posting, and it does work to get the log-in page, but then it fails again after that.


            What I ended up doing, for now, is change the deployment from two-machine to one-machine, eliminating the traffic going between the two EC2 instances. That solved the problem immediately. I suspect that the root of the problem is a communication failure between the two machines that relates to the overall network configuration.


            I suspect that if I want to go back to the two-machine deployment I'll have to learn how to put both of the machines on the same subnet within the Amazon Cloud.


            For now, it works and I'm able to connect both ways.


            I would still like to know how to make this work with a two-machine deployment. Anyone have ideas or suggestions?




            Michael Frankel

            Wizard Consulting Group, Inc.

            • 3. Re: FMS 16 Web Direct over EC2 - can't connect
              Mike Duncan

              You have to use the FQDN when registering a worker machine with the main server. You can verify by logging into the admin console and seeing the hosts listed for all worker machines, including "worker 1" which is always the main machine.

              FM Server will load balance with as many worker machines as it has attached, depending on current users connected to any machine and server load. Once a session is handed off to a worker machine, you remain on that machine until you log out, and any and all session data (global fields, variables, etc) are stored on that machine for the duration.

              With the requirements now upgraded and each worker can handle up to 100 sessions, the need for a second machine is much less, IMO.


              1 of 1 people found this helpful
              • 4. Re: FMS 16 Web Direct over EC2 - can't connect

                Yes, as Mike Duncan says, when configuring machines together in a multi-machine deployment (e.g. when entering master machine's address into worker's deployment screen), you should use addresses that can be accessed from external browser client machines (e.g. FQDNs). Otherwise load balancer can revert to the addresses that were used for configuration (which in this case are internal, and not accessible to the outside). Was going ask you when first reading your post last night if you had a multi-machine deployment here (but wasn't sure at the time if you could do that with AWS instances; now I know).

                2 of 2 people found this helpful
                • 5. Re: FMS 16 Web Direct over EC2 - can't connect
                  Michael Frankel

                  Hi Everyone -


                  I think the mistake I made was using the internal rather than external address for setting up the Worker machine, so that's why removing the Worker machine fixed it.


                  Based on the input provided here, I'm not sure I need a 2-machine deployment, so I'm going to leave it as a single-machine set-up for now.


                  I sincerely appreciate all of the helpful input.



                  Michael Frankel

                  Wizard Consulting Group, Inc.