Sam_McC

Some tips for anyone doing this: Make sure you add a volume mapping for the telegraf.conf You can add this under `Add another Path, Port, Variable, Label or Device` and filling out the host/container paths Add this to the extra parameter: `--privileged -v /:/hostfs:ro -v /run/udev:/run/udev:ro -e HOST_PROC=/hostfs/proc` This is in addition to `--user telegraf:$(stat -c '%g' /var/run/docker.sock)` mentioned in the guide This will help if you're seeing errors about gathering disk tags or disk names. I found it suggested on the telegraf github page Add this to the extra parameter also: `-v /var/run/docker.sock:/var/run/docker.sock` This will help if you're seeing error messages about not being able to connect to the docker daemon. Again, I found it on the telegraf github page And all this to say that this still isn't working for me lol For some reason InfluxDB isn't getting any data, but at least there aren't any errors in the telegraf logs. I'll update this comment when I figure out why InfluxDB isn't getting any stats

Turning NetBIOS on did the trick! Thanks a million.

I just rebooted again and tried "vulpes.local" -- no luck. I tried the IP and surprisingly, it worked! I swear I'd tried that earlier without luck. A follow-up question then... I'm guessing this is a DNS issue then, do you know how I'd get the human-readable name working again?

Oh strange! Attaching them again here vulpes-diagnostics-20241112-1230.zip

Attaching diagnostics here... vulpes-diagnostics-20241112-1230.zip

Initially I had set up the server and was able to access it via LAN with vulpes.local. However once I set my pool + parity drives in the webgui, the webgui stopped working shortly after. I can still ping the server from the LAN Rebooting in safe mode does not fix the issue I'm on v6.12.13 Does anyone know why the webgui wouldn't be working?