• Recent
    • Tags
    • Popular
    • Register
    • Login

    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 Mango 5 Documentation Website

    Error when Checking for Upgrades

    User help
    2
    5
    1.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.
    • M
      mihairosu
      last edited by

      I have Core 2.7.2 on our MainHistorian and the BoilerHistorian (MangoES). Both show the same error. Please see below:

      error 1 of 2.png

      error 2 of 2.png

      1 Reply Last reply Reply Quote 0
      • M
        mihairosu
        last edited by

        Hmm looking through those more closely, I see something having to do with squid. I'll turn off that service tomorrow from our pfSense router and see if that helps.

        1 Reply Last reply Reply Quote 0
        • M
          mihairosu
          last edited by

          I can confirm that with squid transparent proxy, I cannot invoke the upgrade. Removing the squid package fixes it. Nevertheless, I would like to be able to run squid and still be able to upgrade Mango.

          1 Reply Last reply Reply Quote 0
          • phildunlapP
            phildunlap
            last edited by phildunlap

            I am not sure of the particulars of squid, but you can change the base URL that Mango is trying to reach the store at. This is in Mango/overrides/properties/env.properties preferably, but Mango/classes/ by default, and the property is store.url

            It is also entirely possible there was some sort of hiccup... have you tried again?

            1 Reply Last reply Reply Quote 0
            • M
              mihairosu
              last edited by

              I tried multiple times.

              At this time having squid running is not important, and I don't want to change anything manually, since that might be overridden by updates and so on.

              I mainly brought it forward in case y'all are interested in looking into it. I can help test out any patches you may make.

              Searching around it's known that squid can break program updates, so I don't expect you guys to cater to that.

              I'll drop this issue as, as mentioned earlier, it's not important to us.

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