jwillmer
Members
-
Joined
-
Last visited
-
Try to enable verbose logging. It will hopefully tell you why it fails. The "Error connecting to InfluxDB." is written if an exception occurs when trying to write data to influx. You logs show that initially the connection test was successful but in the process of sending data it failed. The reason why it failed is unclear, so please enable verbose logging to get more details.
-
I used the `tailscale set` command to modify the configuration. Is this configuration changes persistent @EDACerton?
-
Issue: I use a Docker container called Traefik. It is a revers proxy that listens on port 80 and 443. All was working when I configured and started it in the previous release. Now I can't start up Traefik any more because it says the ports are in use. Workaround: When changing the http/s ports for Unraid UI I can start Traefik with port 80 and 443. Once Traefik is running I can change back the ports for the Unraid UI.
-
Thank you for the feedback. I have updated the Readme. Hope it works for you now.
-
Overview: Support for the nut-influxdbv2-exporter Docker template. Docker Hub: https://hub.docker.com/r/jwillmer/nut-influxdbv2 GitHub: https://github.com/jwillmer/nut-influxdbv2 Description: nut-influxdbv2-exporter is a container that queries NUT (Network UPS Tools) and then stores the result in a InfluxDBv2.
