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.

Thanks, @phildunlap. Works perfectly.

@dominikj said in Custom base url path:

I think about bad robots that ignore any directives :)

If you are worried about this I would advise firewalling Mango and using a VPN.

Please read https://en.wikipedia.org/wiki/Security_through_obscurity

Ah I see. I do wish there was a "Complete Backup" feature so it would simplify disaster recovery. Maybe someday in the future!

Thanks Phil.

Hi Phil - thanks for the prompt response.

I have a new finding. I now get a response when accessing the http page via command line from the server ( using the wget -p http://localhost:8080 command), but can't access it from any of our other servers running in the same LAN. So now I no longer think this is an issue with the Mango instance, but rather a network/firewall issue most likely.

I will look further into it and report back with my findings after the weekend. Thanks again for the prompt response!

thanks a lot. I tried it again and now it works fine.. thank you for your guide..

Hi jleblancmango,

Hmm. I wonder,

What is store.url set to in your Mango/overrides/properties/env.properties or Mango/classes/env.properties files? On the /ui/administration/modules page, what is your upgrade release channel, and what is your current version? Is there anything in the log file going on?

This can occur if you're on the development channel and the latest were a development release: in that situation it will offer to update the development version endlessly (because we don't put out development modules or cores often, but if we do we'd be updating them frequently, as opposed to an alpha or beta release). But, it shouldn't be happening to you, as the latest core in the store is 3.4.5 currently (no -SNAPSHOT or build timestamp).

Can you check your Mango/logs/ma.log file for what the error is?

Upon investigation, I found Mango online and accessible. I updated it from 3.4.1 to 3.4.3

Hi ChargeRegulator,

Can you post a screenshot? I'm not sure what you mean. The modules would report if they loaded or not and why during startup in the logs. There is no notion of "refresh a license" except for trial licenses with explicit periods.

Hi Mark,

Through Mango, you must update to 2.8.8 before it will let you update to the 3.x series. You will also need to delete the dashboards module before you can update to 3.4 I believe you can do a manual upgrade directly. You can follow the manual instructions here: https://help.infiniteautomation.com/how-to-upgrade-mango/ or you can download the enterprise bundle from the store https://store.infiniteautomation.com/core , unzip that in another directory and copy in your Mango/databases folder from the old Mango. Start it normally and test the upgrade. If you place a store bundle in your Mango/ directory with the name m2m2-core-x.y.z.zip (with proper x.y.z version number) then it will automatically extract the upgrade next time Mango [re]starts Yes you will need to update your license to have a licensed 3.x version of Mango. You could download it and try it out without the license, though. Just keep your old Mango installation handy.

I have ensured the .sh scripts will be executable when downloaded from the store. This was caused by some recent changes we made in the store to make uploading new minor releases easier for us. Sorry for the inconvenience.

Edit: As of 5/7/18 the file permissions in the downloads will be right on Mac / Unix if you unzip it on the command line using "unzip" but may be wrong if you unzip them by right clicking the archive in a file explorer and extracting. We'll iron out this issue sooner than later.

Hi Desmond,

Nothing in the folder structure should have changed. You should be seeking /opt/mango/overrides/properties/env.properties

Yes you can use the ES USB utility to overwrite your env.properties file with one from the drive. Have a look at the copy.properties file, with an env.properties on the USB in the base folder, and a copy.properties in the enabled scripts like

fileToCopy=env.properties targetDirectory=/opt/mango/overrides/properties

It should overwrite your old properties file. You would have to restart Mango to pick up that change.

That's why I'm proxying it, it's my lazy men's way to get it on HTTPS ;-)

@stensma What version of Java are you using? Oracle or OpenJDK?

Thanks. I would like to move the devices to separate data sources, provided the point value history can be moved with it. I'm glad to hear that I can cross that bridge some time after the upgrade.

Certainly!

Check out the ext scripts in Mango/bin/ext-available. You can write an ext script to append that to the JAVAOPTS and it won't be removed at upgrade. Scripts in Mango/bin/ext-enabled are executed at various points in the script lifecycle with $1 like 'start' or 'init' or 'restart' or 'stop'

If you email support@infiniteautomation.com we can email you the files.

Nothing certified but we have not seen any significant difference on any flavor of Linux.

Hi Tom,

It is using both. The H2 database is being used for everything other than point values (also the old HTML reports' data goes into the NoSQL, if installed).