axipher

If I'm not mistaken, InfluxDB 1.3 - 1.8 don't have the web interface enabled, all command line or HTTP API on port 8083. Port 8086 is for data and returns a 404 on my working instance as well. I believe it was version 2 where they brought back the web interface for admin and visualizing.

Thanks for the note on needing to setup 2-factor to be able to access App Passwords. Google finally disabled "less secure apps" on my account so I had to add 2-factor so I can add an app password and get email notifications working again. Also took that opportunity to setup the discord notifications as well as those are pretty easy to set up now.

The change to V2 sent me through a few loops as well since this is on my hobby side so I was more or less blind-sided by it and was playing catch-up which made it feel harder than it was. Good luck on your adventure.

I had some similar issues when my InfluxDB docker updated to v2. Some of my home automation and sensors were all written with 1.8 endpoints and Grafana Dashboards built. I managed to get some of my data working after using this page: https://docs.influxdata.com/influxdb/v2.1/query-data/influxql/ But in the end, I found it much simpler for myself to just have two InfluxDB instances instead, one back on the 1.8 version for all my home automation, Telegraf, other dockers and basic data. Then I have another one using the newer 2.1 for my external web enabled things that I handle myself and can update with new endpoints for data writing and update all my Grafana dashboards. It does mean a little bit of extra tweaking in Grafana based on which version you are accessing and remembering the differences in the queries, but it was much easier to have two InfluxDB versions then convert all my older data that isn't publicly accessible anyway.

I believe traffic stats requires you to also be running a Unifi based router/gateway as well, not just a switch or access point.

Thanks for the Docker solution, I'll keep that in mind for if I try to go back to the current Telegraf docker once we find a solution for the smartmontools.

Which docker updated? InfluxDB has some changes from 1.8 to 2.0 that can break other dockers that assume basic Authorization (from my understanding) I've locked mine to: 'influxdb:1.8' Grafana has some changes form v7 to v8 that can break some dashboards and plugins using lots of the options or thresholds and value mappings I've locked mine to: 'grafana/grafana:8.0.2' Telegraf's most recent update also breaks collection of SMART and Docker statistics. I've locked mine to: 'telegraf:1.20.2-alpine' By locking the versions, then I know updates won't break those connections. It does mean you might miss out on important updates later on, so keeping tabs on those docker's development pages, or on here is still a good idea.

I'm running on the 'telegraf:alpine' default tag and had to make the following changes for it to work, this resulted in running 'Telegraf 1.20.3' per the docker logs. 1) Remove the following 'Post Arguments' under 'Advanced View'. This gets rid of the 'apk error' but also gets rid of 'smartmontools' which means you will lose out on some disk stats for certain dashboards in Grafana. /bin/sh -c 'apk update && apk upgrade && apk add smartmontools && telegraf' 2) Open up '/mnt/user/appdata/telegraf/telegraf.conf' and comment out the following two lines. This gets rid of the 'missing smartctl' errors and also gets rid of the constant error for not being able to access 'docker.sock'. There might be a fix for the docker problem if someone can share it as I find it really useful to monitor the memory usage of each docker from Grafana but currently had to give that up on current version of Telegraf #[[inputs.smart]] #[[inputs.docker]] As others stated, reverting to an older version works as well if the new Telegraf provides nothing new for your use case and would be the recommended route, but I just wanted to document the couple things I had to change to get the latest Telegraf docker running again alongside InfluxDB 1.8 (tag: influxdb:1.8) and Grafana v8 (tag: grafana/grafana:8.0.2). At this point I will probably spend next weekend locking most of my dockers in to current versions and setup a trial Unraid box on an old Dell Optiplex for testing latest dockers before upgrading on my main system.

There can be updates for the 6.4.54 branch in terms of the docker, I'm not sure what they entail exactly without looking at the release note for each one:

I just migrated to a UDM-Pro over the weekend, but previous to that I was using 6.4.54 via UnRaid. I had no problems with the container itself, just issues with actual Unifi Software and its New Dashboard. One thing to keep in mind was that I still had DPI turned off as that was the cause of my Unifi Container ballooning in memory on previous releases and I never turned it back on. Otherwise the 6.4.54 container itself was running no issues for my previous if anyone else was loking for a few more positive reports before they upgraded. Also NGinx Proxy Container worked great for hiding my Unifi Controller behind a sub-domain of mine before I migrated to the UDM-Pro in case anyone is looking for a way to get somewhat HTTPS connection while not at home, or use Wireguard to access your network and then the container from there.

Thanks for this, was driving me nuts every time my Windows VM that runs some scripts reboots, the time is off by my timezone and I need to toggle off/on the auto sync time option. This change in the VM XML fixed that issue.

Something weird has been going on with Grafana. A short time ago, it updated to V8.0 which broke a bunch of my value mappings. I managed to fix those under new templates. Today there was another update for Grafana Docker and now it's back at version 7.5.8 which isn't even on their release page: https://grafana.com/docs/grafana/latest/release-notes/ This change back from 8.0 broke some of my dashboard panels again. for now I've gone and put in "grafana/grafana:8.0.2" as my repository to force the version as the default seems to not be consistent with what version it grabs and v7 to v8 changes a lot of the panel configs.

I get the same thing with "Disk Getting Full" notifications or when I just rebuilt my parity disk, I had to refresh the page to be able to actually dismiss the notifications and not have them come back. Using latest Chrome on Windows 10.

These are my current settings, at least the top main ones. The rest are just folder mappings or the port mappings.

This might be related to a recent Plex release that is upgrading the secure portion to using Let's Encrypt that might not be playing nicely with some browsers. I just tried and it's working for me in Firefox, Edge (Chromium) and Chrome. Not sure if that is fully implemented in the latest docker release and if Plex is forcing a change in the secure connections settings on certain installs. https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/?utm_source=Plex&utm_medium=email&utm_content=network_security_button&utm_campaign=Newsletter_Mar_24_2021_RoW_PP I do clear my cache/cookies once a month or so in all my browsers (CTRL + SHIFT + DELETE) in most to bring up the dialog. Maybe that might clear some things up for you as well if you are using the secure access mode.

I believe for most people, it has been traced back to having DPI turned on, turning off DPI has brought my memory usage under 1 GB, previous to that it would climb to 4-6 GB each week before the weekly CA Auto Backup kicked in and restarted the docker. There were some flags people were adding to limit memory usage, but for me, I just realized I didn't need DPI for home use and gave that up until I can afford a Dream Machine Pro to slot in my rack to replace the Unifi Docker.

Thanks for the reply. Looking at the thread below, I think I'm looking at picking up maybe a LSI 9211-8I mostly because it's just for connecting some spinning 12 TB hard drives and I already have the SFF-8087 to SATA fan-out cables. Would that be a good choice?

I'm running Unraid 6.8.3 right now with plans to upgrade to 6.9.0 once I rebuild a drive that died. I'm on AMD, specifically a 3600x on X570. I came to this thread last year and ended up picking up a AOC-SASLP-MV8 card off eBay to add some more drives, but I'm seeing a few threads and posts recommending against them. I just need to add 4 SATA ports and had alrady picked up some of the SFF-8087 breakout cables. Should I go ahead with the AOC-SASLP-MV8 or find something else? Also the Firmware_3.1.0.15n.zip in the first post is also not working.

Definitely some insight on the choices behind the Unraid and technologies and why certain versions are used instead of the latest or alternatives.

The Free Account for two instances works for this plan, that is what I'm using with a spare account that monitors my UnRaid host and main Windows Server that hosts TeamSpeak and Game Servers.

Thanks for the update to the guide mate

My US-48-G1 runs ay 60 C in my rack alongside a mining rigs and my UnRaid rig in 4U cases. I have a 90 mm fan running at low speed just blowing air across the top of the switch and my USG-3. Without the fan running, it gets up to almost 70 C though, but hovers around there. It is hot to touch at that level and if it does get to 75 C, the internal fan does come on for 10 minutes or so as the fan is only configured for full on or full off at 75 C. The internal fan is pretty loud though, people have come up with commands to turn it on, but no speed control and it turns itself off after the temp is below 75 C for a certain amount of time. There is a large discussion thread on it on the Unifi Forum, I don't have that link handy though. The general consensus was that people aren't happy with the hot temperatures of their 48-port non-POE switches. I'm not sure what the safe temperatures of the chips being used in the Switch are and if running at 60 - 70 C is actually detrimental for long term reliability or not. Personally I prefer my electronics to be at most warm to the touch on the cases in case a cable sits against it or my hand grazes by it while working on something else so I installed the extra fan. Once the warranty runs out on my switch, I'll likely open it up and swap in a couple Noctua fans with a low noise adapter spliced in to some constant 12 V in the switch somewhere. I'll try to remember to post a link to that here if I do it.

To build on this reply, I have a User-Script setup like the following that I was using when I had DPI turned on in my Unifi-Controller causing some really high memory usage over time. So I had this script set to run once a week: #!/bin/bash #arrayStarted=true docsrunning=$(docker ps | awk '{ print $2}') echo "These Dockers are running" echo $docsrunning echo "Is 'unifi-controller' running?" if [[ "$docsrunning" == *"unifi-controller"* ]]; then echo "Looks like it is, triggering a restart to reclaim memory" echo "" docker restart unifi-controller fi It could be cleaned up to include the docker name as a variable and stuff, but its something that someone can use as a reference for restarting dockers.

I know the recent controller version 6 broke some things, I think the new setup I have now has a Network that has a VLAN associated with it and then a wireless network SSID configured that uses that configured network, I have my Guest network shown for the wireless example, but "3_Guest" is set up similar to "5_IoT_Cloud_Access". If I connect my phone to my "Cayde-Guest" SSID that is connected to network "3_Guest" on VLAN 10, I only get internet access and can't access other devices or my Chromecasts in the network. Similarly, if I configure a port to be only the "3_Guest" or "5_IoT_Cloud_Access" networks and plug in my laptop to that port, I also get only internet access. As for wired devices, I have the ports on my switch that I'm plugging IOT devices configured to only have the IOT network with a VLAN tagged to that port So that my Philips Hue Bridge for example is plugged in to a port that only has my IOT network turned on for it:

I was taking my monthly look at my server to see where my SSD's were at in regards to TB Written (Data units written) as most SSD's have a limited warranty of something like 5 years of 320 TB Written in the case of my SX8200 Pro. There is currently a Warranty Period field where you can enter a warranty that is limited to 5 years: - Unknown - 6 Months - 12 Months - 24 Months - 36 Months - 48 Months - 60 Months It would be nice to expand that list since some drives have 6+ years or allow a custom entry with just a number field and a dropdown for months or years. It would also be nice to have a secondary warranty condition that can be linked to the Data units written so I can enter in a value in TBW for an SSD. Finally, it would be great to have this added to the Alerter/Notifier and its settings to be able to be able to trigger alerts and emails when a drive is nearing it's warranty, say 10% away from either of the defined warranty periods, and then another time when it has surpassed either defined warranty period.