I believe it's this item, as seen here.

Use GUID as the default session cookie name

@mihairosu

After running certbot, it created the certificate and key in the /etc/letsencrypt/live/fqdn.com/ directory, I was able to get it to work with the following nginx configuration:

server {

listen 443 ssl;
server_name fqdn.com;
root /opt/mango/overrides/web/;
index index.html;

ssl_certificate /etc/letsencrypt/live/fqdn.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/fqdn.com/privkey.pem;

include /etc/letsencrypt/options-ssl-nginx.conf;

location / {
proxy_pass http://127.0.0.1:8080/;
proxy_http_version 1.1;

# Inform Mango about the real host, port and protocol

proxy_set_header X-Forwarded-Host $host:$server_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}

}

Here's how I did it.

 <!-- Get point values -->
 <ma-point-values point-xid="hallsFanInletAirTemp" point="inletAir"></ma-point-values>

 <!-- Create a way to manupulate point values to 12 previous hours and update.  In this example, I am getting previous 12 hours at a 1 minute average.  You only have to do this once -->

<ma-now update-interval="1 minutes" output="to"></ma-now>
<ma-calc input="to | moment:'subtract':12:'hours'" output="from"></ma-calc>

<!-- Manipulate the actual values of the point.  This code can be multiplied for as many points as you want -->

<ma-point-values point="inletAir" values="inletAirValues" from="from" to="to" rollup="AVERAGE" rollup-interval="1 minutes">
</ma-point-values>

 <!-- Display Chart -->
	<ma-serial-chart 
                style="height: 500px; width: 100%" 
                series-1-values="inletAirValues" 
                series-1-point="inletAir" 
                series-1-color="green" 
                series-1-axis="left"
                series-1-type="line"
                legend="true" 
                baloon="false"
                options="{
                    valueAxes:[
                        {
                            axisColor:'black', 
                            color:'black', 
                            title: 'Temperature °F', 
                            titleColor: 'black', 
                            minimum:-40, 
                            maximum:140,
                            fontSize:26,
                            titleFontSize:26,
                        }, 
                    ]
                }"
            >
            </ma-serial-chart>

Try this to read a point, like the Voltage from your meter. You can get here from the Data Sources page. See my picture below:

Oh, your modbus settings have to match the meter, of course, like the bit rate, parity, etc.

One more thing, you have to turn off the serial data source to do the test, or else i'll throw an error because it's busy.

I don't have any proof as I have not collected any data but I can say the following:

Many months ago, out disk was getting full with a Purge data setting of 4-5 weeks.

Then the disk was starting to get full again, and I reduced that further to a 10 days.

We have not added any additional data points during this time, and the disk is getting full again.

I just realized that the purge settings probably only affect the NoSQL database, but it's the H2 database that is causing us issues.

Can we reset this database cleanly and start again, which I imagine will hold up well for another number of years without trouble. I have instructions for how to delete and restore the database, but that also removes the configuration settings. Is is possible to remove only the data history while keeping the configuration?

What is the difference between core-database and configuration backups anyway?

This script used to work just fine, but is throwing errors every night since 10/16/2019 at the exact time its running 23:59:57.

/*
//Script by Phil Dunlap to automatically generate lost history
if( my.time + 60000 < source.time ) { //We're at least a minute after
  var metaEditDwr = new com.serotonin.m2m2.meta.MetaEditDwr();
  metaEditDwr.generateMetaPointHistory(
      my.getDataPointWrapper().getId(), my.time+1, CONTEXT.getRuntime(), false);
  //Arguments are, dataPointId, long from, long to, boolean deleteExistingData
  //my.time+1 because first argument is inclusive, and we have value there
}
//Your regular script here.*/


return CwConsumed.value-CwConsumed.ago(DAY, 1) //Subtracts this moment's gallons used minus one day ago

Here's the error:

'MetaDataSource': Script error in point "Main Historian - DHW Consumed Daily Count": Expected } but found eof return DhwConsumed.value-DhwConsumed.ago(DAY, 1) //Subtracts this moment's gallons used minus one day ago ^ at line: 12, column: 129Add comment

For some reason, during this particular time period, the data is not syncing.

Data Source:
MangoES
core 3.34

Data Destination:
Mango Enterprise
core 3.34

Data is sent through Mango Persistent TCP Sync.

Source Prior To Sync:

Destination Prior to Sync:

Syncing:

Log from Source:

INFO  2018-04-20T09:12:02,021 (com.serotonin.m2m2.persistent.pub.PersistentSenderRT.raiseSyncCompletionEvent:301) - Points: 159, sent 773 requests, synced 383631 records, target overcounts: 9, response errors: 0, elapsed time: 1m15s

Source Post Sync (I added more points):

Destination Post Sync:

Oh sorry we are running core core 3.3.4 - MangoES.

Which backup should I restore, NoSQL or SQL. I am guessing SQL, but I know restoring NoSQL could also work, or am I wrong?

I have not tried to restore yet, so there aren't any other problems.

Synchronize history prior to is set at 1 minute.

I've taken a representative sample of points, and checked again today. It looks like all points are affected.

Here's the data again as of today, but with a lot more points.. Well if we cannot resolve this by May 3, it will be purged from the source. It's not the end of the world, but if you are interested in investigating it, it might help you find issues. I don't know if this is a problem on our end either.

Still at source:

Still missing:

select count(*) from pointValues; = 0

mrosu@22historian:~$ du -sh /opt/mango/databases/*
3.2G /opt/mango/databases/mah2.h2.db
4.0K /opt/mango/databases/mah2.lock.db
12K /opt/mango/databases/mah2.trace.db
47M /opt/mango/databases/mangoTSDB
1.2M /opt/mango/databases/mangoTSDBAux
12K /opt/mango/databases/reports

Hey @joeamiraglia ,

Okay I confirmed all of that and it seems like the guest user is working okay.

Let's begin with this data point which no longer updates:

member2BoilerStatusCode

The data flows as follows:

device -> via ModbusRTU to MangoES -> via Publisher to Enterprise Mango.

• ModbusRTU to MangoES: data is successfully retrieved

• Publisher to Enteprise Mango: data has not updated since 2/7/2016

I really wish I could attach images on here but you guys have some problems with IMGUR apparently, anyway.

• MangoES: Data updates correctly visible on the watch list, it is not disabled.
• MangoES Publisher: member2BoilerStatusCode shows up on the "Published data points"

I tried removing it and re-adding it to the publisher and that did not help.
I even tried changing the data point template to update when timestamp changes and that did not resolve it.

I don't see any problems with the history synchronization otherwise in the publisher status or events.

I'm not sure how to diagnose this.

One of the data points is not publishing. I don't know to how many this is happening but if we can figure this one out, I know how to rectify the rest:

This is coming from a ModbusRTU source into a MangoES, which is published to an Enterprise Mango install

I cannot seem to be able to post images on here due to Imgur limits, but here's what I confirmed.

• MangoES is pulling data via Modbus

• MangoES has the data in the Publisher

• MangoEnterprise is not receiving this data point

Many other data points are being sent correctly.

I tried to REMOVE, SAVE and then ADD the data point again, and it did not resolve the situation.

Hello,

It has been a long time since I've had to mess with guest access and permissions, so I'm a bit lost.

We are running on Core 5.6.3

Current Issue

Our headless dashboards do not show all of the data points (some appear and some do not) and I cannot tell why. Some of the data points are meta data points and some are not.

Configured Login

These dashboards were set up to automatically log in using user guest and password guest through the URL as follows:

https://internal.dns/ui/plumbing_dhw_overview?autoLoginUsername=guest&autoLoginPassword=guest1234&autoLoginStoreCredentials

I checked one of the data points which was not visible and it has the following permissions:

View point & Value:
Superadmins (check)
Users (check)
Anonymous (unchecked)

P.S. I tried to attach an image but there was an error "Imgur is temporarily over capacity. Please try again later."

Resolution?

I assume something has changed since the last update I performed.

Previously we were running 5.6.2.

I assume it's an issue with permissions

@joeamiraglia

Just wanted to confirm that the latest update as of a couple of days ago, was successful.

@joeamiraglia

Hey Joe,

Great, thanks for the heads up. I will just wait for v5.5.3.

I'm going to revert to a backup until there's a resolution.

I tried to update Core and all modules from 5.4.1 to 5.5.2 and now Mango won't start up.

See link to ma.log file.

edit: nevermind just had to clear all browsing data.

@CraigWeb

Uh oh, that's a mistake on my part.

Thanks for catching that!

@MattFox
Nah I did get that. I just thought from all the information I've received, it seems to me that our current configuration should also work just fine.

Anyway, I may have to resort to that; It's a good option.