• Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

    HTTP Receiver Data Source Blocked

    User help
    2
    8
    173
    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.
    • R
      Robmalone last edited by

      Hi all,
      I am trying to get data from one instance of mango to another via http publisher. Everything on the publisher end seems ok but the receiver end is showing it as blocked. I have checked my windows firewall and everything seems good. I even turned off the firewall for a few minutes to test but no change.
      Any ideas? Very likely something obvious I've overlooked.
      Thanks,
      Rob
      490e6784-e37f-463d-a013-9cbf8e9d37bc-image.png

      1 Reply Last reply Reply Quote 0
      • MattFox
        MattFox last edited by MattFox

        have you set your url?
        hang on, misread that.
        Turn your whitelist off first. best to see if you can push something in.
        Check your publisher settings. don't forget remote url path needs /httpd

        Fox

        Do not follow where the path may lead; go instead where there is no path.
        And leave a trail - Muriel Strode

        1 Reply Last reply Reply Quote 0
        • R
          Robmalone last edited by

          Thanks @MattFox .
          Is httpd a typo? Should that be httpds? Hopefully not and that's the problem!
          I'll give your suggestions a go and let you know.

          1 Reply Last reply Reply Quote 0
          • MattFox
            MattFox last edited by

            it may be httpds...

            I recommend you test with postman first.
            Get an extract of the data you are trying to send with webhook.site from your publisher mango.
            Then fire that data with postman to.your secondary mango.
            Convenient way to test endpoints.

            Fox

            Do not follow where the path may lead; go instead where there is no path.
            And leave a trail - Muriel Strode

            1 Reply Last reply Reply Quote 0
            • R
              Robmalone last edited by

              @MattFox I have used webhooks.site to test the messages. All are being sent and received ok but still nothing coming into the server. The data source still says blocked.
              Is there somewhere I need to open ports or anything like that?

              1 Reply Last reply Reply Quote 0
              • MattFox
                MattFox last edited by MattFox

                Hang on, you are using SSL...
                What is the port number you have configured to access mango via straight http??
                Is it 8080?
                If so your publisher needs that in the url.

                destination.mango:8080/httpds
                

                That is what I believe may be the issue...

                Fox

                EDIT: I really need to stop using my mobile for viewing images...
                Since the HTTP receiver is blocked. I would check system logs and maybe check running permissions for mango. If you are using windows there my be a chance you are indeed fighting windows firewall.
                Look at the logs first, post them here in code tags, especially ma.log where and when you enable then disable the http receiver.
                That will give us more info...

                Fox

                Do not follow where the path may lead; go instead where there is no path.
                And leave a trail - Muriel Strode

                R 1 Reply Last reply Reply Quote 0
                • R
                  Robmalone @MattFox last edited by

                  @mattfox My apologies for the delay in getting back to you. It was indeed a windows firewall issue. Thanks for the help as always.

                  MattFox 1 Reply Last reply Reply Quote 0
                  • MattFox
                    MattFox @Robmalone last edited by

                    @robmalone anytime

                    Do not follow where the path may lead; go instead where there is no path.
                    And leave a trail - Muriel Strode

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