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

    Solved Ubiquiti STUN Communication

    IT Discussion
    ubiqui unifi controller unifi vultr
    4
    16
    4.7k
    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 @Mike Davis
      last edited by

      @mike-davis said in Ubiquiti STUN Communication:

      I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

      Did you enable the Vultr Firewall?

      Did you adjust the Debian/Ubuntu Firewall to allow the traffic?

      Way too much not said here.

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

        @dbeato said in Ubiquiti STUN Communication:

        @mike-davis said in Ubiquiti STUN Communication:

        I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

        So you didn't open any of those ports I listed?

        You do not normally need them.

        dbeatoD 1 Reply Last reply Reply Quote 0
        • dbeatoD
          dbeato @JaredBusch
          last edited by

          @jaredbusch said in Ubiquiti STUN Communication:

          @mike-davis said in Ubiquiti STUN Communication:

          I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

          Did you enable the Vultr Firewall?

          Did you adjust the Debian/Ubuntu Firewall to allow the traffic?

          Way too much not said here.

          Yes, Vultr Firewall is enabled and Debian Firewall is adjusted. What are you missing?

          1 Reply Last reply Reply Quote 0
          • dbeatoD
            dbeato @JaredBusch
            last edited by

            @jaredbusch said in Ubiquiti STUN Communication:

            @dbeato said in Ubiquiti STUN Communication:

            @mike-davis said in Ubiquiti STUN Communication:

            I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

            So you didn't open any of those ports I listed?

            You do not normally need them.

            What don't you normally need them? 8080 and 8443 at a minimum correct?

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

              @dbeato said in Ubiquiti STUN Communication:

              @jaredbusch said in Ubiquiti STUN Communication:

              @dbeato said in Ubiquiti STUN Communication:

              @mike-davis said in Ubiquiti STUN Communication:

              I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

              So you didn't open any of those ports I listed?

              You do not normally need them.

              What don't you normally need them? 8080 and 8443 at a minimum correct?

              Correct.

              dbeatoD 1 Reply Last reply Reply Quote 0
              • dbeatoD
                dbeato @JaredBusch
                last edited by

                @jaredbusch said in Ubiquiti STUN Communication:

                @dbeato said in Ubiquiti STUN Communication:

                @jaredbusch said in Ubiquiti STUN Communication:

                @dbeato said in Ubiquiti STUN Communication:

                @mike-davis said in Ubiquiti STUN Communication:

                I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

                So you didn't open any of those ports I listed?

                You do not normally need them.

                What don't you normally need them? 8080 and 8443 at a minimum correct?

                Correct.

                But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
                https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setup

                https://help.ubnt.com/hc/en-us/articles/115006809068-UniFi-Guest-Portal-Customization-Hotspot-System#comparison

                https://help.ubnt.com/hc/en-us/articles/205202640-UniFi-Guest-Portal-Promotional-URL-Automatic-Redirection

                With regards to STUN though, you believe is not needed then?

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

                  @dbeato said in Ubiquiti STUN Communication:

                  @jaredbusch said in Ubiquiti STUN Communication:

                  @dbeato said in Ubiquiti STUN Communication:

                  @jaredbusch said in Ubiquiti STUN Communication:

                  @dbeato said in Ubiquiti STUN Communication:

                  @mike-davis said in Ubiquiti STUN Communication:

                  I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

                  So you didn't open any of those ports I listed?

                  You do not normally need them.

                  What don't you normally need them? 8080 and 8443 at a minimum correct?

                  Correct.

                  But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
                  https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setup

                  https://help.ubnt.com/hc/en-us/articles/115006809068-UniFi-Guest-Portal-Customization-Hotspot-System#comparison

                  https://help.ubnt.com/hc/en-us/articles/205202640-UniFi-Guest-Portal-Promotional-URL-Automatic-Redirection

                  With regards to STUN though, you believe is not needed then?

                  Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
                  https://en.wikipedia.org/wiki/STUN

                  dbeatoD 2 Replies Last reply Reply Quote 3
                  • dbeatoD
                    dbeato @JaredBusch
                    last edited by

                    @jaredbusch said in Ubiquiti STUN Communication:

                    @dbeato said in Ubiquiti STUN Communication:

                    @jaredbusch said in Ubiquiti STUN Communication:

                    @dbeato said in Ubiquiti STUN Communication:

                    @jaredbusch said in Ubiquiti STUN Communication:

                    @dbeato said in Ubiquiti STUN Communication:

                    @mike-davis said in Ubiquiti STUN Communication:

                    I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

                    So you didn't open any of those ports I listed?

                    You do not normally need them.

                    What don't you normally need them? 8080 and 8443 at a minimum correct?

                    Correct.

                    But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
                    https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setup

                    https://help.ubnt.com/hc/en-us/articles/115006809068-UniFi-Guest-Portal-Customization-Hotspot-System#comparison

                    https://help.ubnt.com/hc/en-us/articles/205202640-UniFi-Guest-Portal-Promotional-URL-Automatic-Redirection

                    With regards to STUN though, you believe is not needed then?

                    Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
                    https://en.wikipedia.org/wiki/STUN

                    So that's the way I am going to approach it.

                    1 Reply Last reply Reply Quote 0
                    • dbeatoD
                      dbeato @JaredBusch
                      last edited by

                      @jaredbusch said in Ubiquiti STUN Communication:

                      @dbeato said in Ubiquiti STUN Communication:

                      @jaredbusch said in Ubiquiti STUN Communication:

                      @dbeato said in Ubiquiti STUN Communication:

                      @jaredbusch said in Ubiquiti STUN Communication:

                      @dbeato said in Ubiquiti STUN Communication:

                      @mike-davis said in Ubiquiti STUN Communication:

                      I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

                      So you didn't open any of those ports I listed?

                      You do not normally need them.

                      What don't you normally need them? 8080 and 8443 at a minimum correct?

                      Correct.

                      But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
                      https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setup

                      https://help.ubnt.com/hc/en-us/articles/115006809068-UniFi-Guest-Portal-Customization-Hotspot-System#comparison

                      https://help.ubnt.com/hc/en-us/articles/205202640-UniFi-Guest-Portal-Promotional-URL-Automatic-Redirection

                      With regards to STUN though, you believe is not needed then?

                      Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
                      https://en.wikipedia.org/wiki/STUN

                      How can it mark your post as the solution?

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

                        @dbeato said in Ubiquiti STUN Communication:

                        @jaredbusch said in Ubiquiti STUN Communication:

                        @dbeato said in Ubiquiti STUN Communication:

                        @jaredbusch said in Ubiquiti STUN Communication:

                        @dbeato said in Ubiquiti STUN Communication:

                        @jaredbusch said in Ubiquiti STUN Communication:

                        @dbeato said in Ubiquiti STUN Communication:

                        @mike-davis said in Ubiquiti STUN Communication:

                        I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

                        So you didn't open any of those ports I listed?

                        You do not normally need them.

                        What don't you normally need them? 8080 and 8443 at a minimum correct?

                        Correct.

                        But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
                        https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setup

                        https://help.ubnt.com/hc/en-us/articles/115006809068-UniFi-Guest-Portal-Customization-Hotspot-System#comparison

                        https://help.ubnt.com/hc/en-us/articles/205202640-UniFi-Guest-Portal-Promotional-URL-Automatic-Redirection

                        With regards to STUN though, you believe is not needed then?

                        Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
                        https://en.wikipedia.org/wiki/STUN

                        How can it mark your post as the solution?

                        Tell @scottalanmiller to do it because that is a glaring whole in this plugin. Has been reported, but unactioned for years now.

                        dbeatoD 1 Reply Last reply Reply Quote 2
                        • dbeatoD
                          dbeato @JaredBusch
                          last edited by

                          @jaredbusch said in Ubiquiti STUN Communication:

                          @dbeato said in Ubiquiti STUN Communication:

                          @jaredbusch said in Ubiquiti STUN Communication:

                          @dbeato said in Ubiquiti STUN Communication:

                          @jaredbusch said in Ubiquiti STUN Communication:

                          @dbeato said in Ubiquiti STUN Communication:

                          @jaredbusch said in Ubiquiti STUN Communication:

                          @dbeato said in Ubiquiti STUN Communication:

                          @mike-davis said in Ubiquiti STUN Communication:

                          I'm hosting my unifi controller on vultr and I didn't have to make any port changes that I remember.

                          So you didn't open any of those ports I listed?

                          You do not normally need them.

                          What don't you normally need them? 8080 and 8443 at a minimum correct?

                          Correct.

                          But I opened the 8880 and 8843 for HTTP and HTTPS for Guest Hotspot portal. Usually not needed for others but in this case it was needed.
                          https://help.ubnt.com/hc/en-us/articles/115000871247-UniFi-Social-Media-Guest-Authentication#controller setup

                          https://help.ubnt.com/hc/en-us/articles/115006809068-UniFi-Guest-Portal-Customization-Hotspot-System#comparison

                          https://help.ubnt.com/hc/en-us/articles/205202640-UniFi-Guest-Portal-Promotional-URL-Automatic-Redirection

                          With regards to STUN though, you believe is not needed then?

                          Should not be as your controller is not behind NAT. There is not point to STUN unless NAT is involved.
                          https://en.wikipedia.org/wiki/STUN

                          How can it mark your post as the solution?

                          Tell @scottalanmiller to do it because that is a glaring whole in this plugin. Has been reported, but unactioned for years now.

                          Hey @scottalanmiller can you mark Jared's post with Wikipedia on it for the solution. I cannot for the life of me mark it as a solution.

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