@girish worked like a charm! Thanks!

@my1water it appears to be a one off issue with the screen sharing session I was using while trying to configure the dashboard - this can be closed, thanks!

Yeah, you likely don't want localhost you want the uuid of the installation as the hostname since that's what's exposed in the docker virtual network.

@jimcavoli said in How to monitor Cloudron and Cloudron-apps with Grafana ?:

fed via collectd in case you're curious

but maybe I should focus on Collectd since my goal is to monitor IPTables

@ChristopherMag This should be fixed now with the latest package. I found that we have to set GF_PLUGIN_DIR env var or pass --pluginDir separately for the CLI tool. The server reads configs from custom.ini but the CLI does not (there's probably some good reason for this discrepancy).

@girish said in Safe to replace admin user?:

It's best to keep the original admin user

Duly noted. 😅

never have to login again after giving your Cloudron user admin previliges.

Yeah, oddly enough I found the LDAP setting in my new admin user as well now, so the whole thing might've been a brainfart on my part.

Is there anything in the logs? I have never used Loki, so not sure what could be going wrong. Are you able to add other sources or just loki is the problem?

@rmdes Magic! 🙂

Right, /app/data/custom.ini is where the users customizations go. What db were you using in your existing installation? The cloudron package uses postgres. To get the DB connection credentials, you can go to the Terminal of the app and do env | grep CLOUDRON_POSTGRES. You can also click the postgres button on the top and it will paste the CLI needed to access postgres.