ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    FOP2 - can't connect from CenturyLink

    Scheduled Pinned Locked Moved IT Discussion
    13 Posts 4 Posters 500 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch @Dashrender
      last edited by

      @Dashrender said in FOP2 - can't connect from CenturyLink:

      I am using the standard port 4445.

      ............

      FFS don't confuse things.....

      You do not access FOP2 on a specific port.

      You use https://pbx.domian.com/fop2

      Yes, FOP2 itself uses port 4445 behind the scenes.

      DashrenderD 1 Reply Last reply Reply Quote 2
      • JaredBuschJ
        JaredBusch @travisdh1
        last edited by

        @travisdh1 said in FOP2 - can't connect from CenturyLink:

        I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

        This is what you see when you connect to FOP2
        aa37297d-2e20-4534-98c8-bfde6d0fc78f-image.png

        1 Reply Last reply Reply Quote 1
        • DashrenderD
          Dashrender @travisdh1
          last edited by

          @travisdh1 said in FOP2 - can't connect from CenturyLink:

          I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

          I can get to port 443 - my FreePBX page loads just fine.

          JaredBuschJ scottalanmillerS 2 Replies Last reply Reply Quote 0
          • DashrenderD
            Dashrender @JaredBusch
            last edited by

            @JaredBusch said in FOP2 - can't connect from CenturyLink:

            @Dashrender said in FOP2 - can't connect from CenturyLink:

            I am using the standard port 4445.

            ............

            FFS don't confuse things.....

            You do not access FOP2 on a specific port.

            You use https://pbx.domian.com/fop2

            Yes, FOP2 itself uses port 4445 behind the scenes.

            Thanks, you're right, but I still have the issue.

            1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @Dashrender
              last edited by

              @Dashrender said in FOP2 - can't connect from CenturyLink:

              @travisdh1 said in FOP2 - can't connect from CenturyLink:

              I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

              I can get to port 443 - my FreePBX page loads just fine.

              Said above screenshot is connecting to your FOP2 instance.

              That wasn't the point of my reply..

              The way you bought in port 4445 implied that you and your users are connecting to https://pbx.domain.com:4445

              1 Reply Last reply Reply Quote 1
              • scottalanmillerS
                scottalanmiller @Dashrender
                last edited by

                @Dashrender said in FOP2 - can't connect from CenturyLink:

                @travisdh1 said in FOP2 - can't connect from CenturyLink:

                I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

                I can get to port 443 - my FreePBX page loads just fine.

                FOP2 should be on that port along with it.

                DashrenderD 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  Is it working when you connect from other locations?

                  1 Reply Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender @scottalanmiller
                    last edited by

                    @scottalanmiller said in FOP2 - can't connect from CenturyLink:

                    @Dashrender said in FOP2 - can't connect from CenturyLink:

                    @travisdh1 said in FOP2 - can't connect from CenturyLink:

                    I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

                    I can get to port 443 - my FreePBX page loads just fine.

                    FOP2 should be on that port along with it.

                    it is for me, and JB.
                    My users get to the page, but it does the count up loading thing, then never completes - hence the error screens at the top.

                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch @Dashrender
                      last edited by

                      @Dashrender said in FOP2 - can't connect from CenturyLink:

                      @scottalanmiller said in FOP2 - can't connect from CenturyLink:

                      @Dashrender said in FOP2 - can't connect from CenturyLink:

                      @travisdh1 said in FOP2 - can't connect from CenturyLink:

                      I bet CenturyLink is blocking the port for some reason. Can you easily try port 80 or 443 server side?

                      I can get to port 443 - my FreePBX page loads just fine.

                      FOP2 should be on that port along with it.

                      it is for me, and JB.
                      My users get to the page, but it does the count up loading thing, then never completes - hence the error screens at the top.

                      It is for everyone.

                      Your users simply are not getting the log in box, which is connecting to port 4445

                      1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch
                        last edited by

                        Once you are logged in to FOP2, port 4445 is the only outbound port from the local PC.

                        3a2648d7-9840-4953-a5fd-429e24e6a4e4-image.png
                        c8293887-6bf3-4966-8a0e-9b756990fe81-image.png

                        1 Reply Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender
                          last edited by

                          OK - JB to the rescue again.

                          He saw I was marking my allowed IPs as Local - FreePBX doesn't know the 4445 service, so it's not allowed to be part of Local as far as the firewall is concerned.

                          So two options exist -

                          1. mark allowed IPs as Trusted, not Local
                          2. create a custom service under the firewall, and set it as a local service, then IPs marked as Local will get access.

                          Thanks @JaredBusch

                          1 Reply Last reply Reply Quote 2
                          • 1 / 1
                          • First post
                            Last post