@Danp Thanks, that makes sense. Perhaps is should show "Premium Feature" instead of "netdata plugin is necessary" when using the free versions.

@fred974 said in S3 Remote:

HAproxy in pfSense

I was hoping to avoid this method as my pfsense is not connected at 10G. Thank you for the clarification.

@fred974 I am not really clear on how you solved it. I am still getting "Error calling AWS.S3.putObject: self signed certificate" using xo-server 5.74.1 / xo-web 5.77.0. and the S3 target system is TrueNAS 12.0 U2

Related to this, when I had tried MinIO it did not like the self signed certificate. Can that be a toggle option to make internal testing easier?

In addition to the write ups in the Wiki, would it be ok to link my YouTube tutorial videos that I have made on many aspects of the project?

@kevdog The issue with Netdata that caused it to be removed from FreeNAS was specifically a memory leak in the FreeBSD version of Netdata.

https://github.com/netdata/netdata/issues/7356

ncmans created this issue in netdata/netdata

closed Re-introduce Netdata to FreeNAS #7356

@Danp Thanks, that makes sense. Perhaps is should show "Premium Feature" instead of "netdata plugin is necessary" when using the free versions.

I am getting "netdata plugin is necessary" when I mouse over the "Enable Advances Live Telemetry" option. The host is a fully patched XCP-ng 8 and I have tested with both XOA Free and the the self compiled XOA both are running xo-server 5.53.0 & xo-web 5.53.3. I manually installed netdata-ui.x86_64 & netdata.x86_64 via command line and netdata is working fine and is accessible via http://host_address:19999

I did reboot the XCP-host and both the XOA and the problem persists, what should I check next?