EDACerton

You might want to try the "Enhanced Log" plugin available in CA. It adds a lot of filtering options, and will be getting even better :)

Here's what you can use if you to to Plugins -> Install Plugin in the WebGUI: https://raw.githubusercontent.com/unraid/unraid-tailscale/2025.04.17/plugin/tailscale.plgI keep the plugins supported for the last two minor releases of Unraid (currently, that's 7.0 and 7.1). After that, I stop testing with the older versions, so they're marked "incompatible" since I might start doing things that don't work in earlier OS versions (I have had this happen before). I wish there were a way to make CA aware of the earlier versions of the plugins for 6.12.x, etc... but unfortunately that's not a feature that exists :(

I just released 2025.06.13. This version includes a completely redone backend in go, which is much easier to manage/maintain, and also provides a better framework for future features (I have a few in mind already that this will make possible). I've also improved the display in the WebGUI. The tables are now more compact, and there are some new filter options (including a date/time range). The interface now opens to the last 30 minutes of activity, then you can adjust the filters to your needs.

2025.06.08 has been released, which includes various improvements to the backend processing, and also a new and improved display. @Niklas , I haven't forgotten about you, the backend improvements in this release are the first phase of improving how disks are detected/handled. :)

IP addresses don’t work with Tailscale serve/TSDProxy/reverse proxies… they rely on the server name provided by the client to know how to route the request. That is working by design.

MagicDNS names won't work if it's turned off on the client, so you'll need to turn that back on. After that, I'd restart the client and try again.

Do you have Tailscale DNS turned on for your client? (Not on Unraid, on your laptop/phone/etc.)

I don't keep any 6.x test boxes anymore. Unraid 7 has been out since January.

For until Squid can issue a fix, here's a workaround: Remove CA from the plugins page, then go to "Install Plugin" on the same page and use this: https://raw.githubusercontent.com/unraid/community.applications/4e0da5c4c810188735683fab63ef1a676dac30a2/plugins/community.applications.plg That will install the previous version of CA. Once you've done that, you can either: Stay on that version until a new update is released, or Pin an application (click on Info for an app, then Pin App). Once you have an app pinned, you should be able to update safely.

Someone posted this on Discord: [29-May-2025 19:26:32 America/Chicago] PHP Fatal error: Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in /usr/local/emhttp/plugins/community.applications/include/exec.php:1574 Stack trace: #0 /usr/local/emhttp/plugins/community.applications/include/exec.php(1574): in_array(true, NULL) #1 /usr/local/emhttp/plugins/community.applications/include/exec.php(117): areAppsPinned() #2 {main} thrown in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 1574

You don't need Label Manager for that, just add the proper labels to your Compose file: https://almeidapaulopt.github.io/tsdproxy/docs/docker/

[random, unidentifiable value] installed multiple plugins. There's no privacy implication to that. It doesn't make it less anonymous.

Actually, no. Using md5 would not provide privacy like crc32 does. Here's why: The Unraid flash GUID is 96 bits. md5 provides a 128-bit hash -- so reverse engineering that back to the original GUID would be trivial (since it'll provide a unique hash per GUID). crc32, however, provides 32 bits of data. That means that, for every 32-bit clientID, there are 2^64 = 18,446,744,073,709,551,616 possible flash GUIDs that it could have come from -- and no way to figure out which one it was. However, let's be even more particular, since technically the first 32 bits of the flash GUID aren't completely random (they're the USB vendor and device IDs from the flash drive). That leaves us with 2^32 (the total number of flash drive models in existence). For the sake of argument, then, let's go with an absurdly low number and assume that there are only 10 flash drive models in the world. That leaves us with 2^32 * 10 = 42,949,672,960 possible GUIDs. (And in reality, that 42-billion number is actually much, much larger.) And finally, if we're going to make comparisons to browser cookies, a more accurate analogy would be the User-Agent string that your browser sends with every request, to every web site, which provides the running browser/version and OS of the device.

I’m going to defer to staff on how to handle this. You chose to delete the original repositories (not even archive them — delete them, specifically to deny users the ability to install them), disrupting users, then returned because you didn’t like work that was done.

As I said: I posted a link to the code. You're welcome to inspect it.

I'm not going to debate this any further in the thread... LT is aware of how I handle metrics, I discussed the technique (including the use of the GUID) with them a long time ago. Not to put too fine a point on it, but -- I didn't even use these plugins before they were deleted. I don't need them. I revived them to be helpful to the community. Having data on how many installs there are, etc. helps me prioritize the personal time that I put into maintaining these plugins for all of you.

As I said, this system has been discussed with staff previously. Usage reporting in software is commonly opt-out; it’s an accepted technique across the industry. Some software doesn’t even give you an option anymore.

The plugin uses the same usage reporting system as my other plugins, which I have previously discussed with staff. No personal information is collected with the metrics -- I don't even store the inbound IP with the metrics data. The closest thing is the clientId, which is the flash GUID (128 bytes of essentially random data) passed through crc32 (reducing it to 32 bits), so there is no possible way that I could reconstruct the flash GUID from the client ID (and even then, that's not personal information either). You're welcome to inspect the process if you have any doubts: https://github.com/dkaser/unraid-fileactivity/blob/87848990548fe8d402c0c7ceafdc6fb98ef66477/src/usr/local/emhttp/plugins/file.activity/include/FileActivity/Utils.php#L110 (And also, the reporting doesn’t run immediately on installation, and the setting is clearly shown in the options.)

Fixed with 2025.05.23 :)

I don’t have any 6.x test boxes anymore. I will be following my usual support pattern: current and previous minor releases. As of right now, that’s 7.0 and 7.1.

I have republished both this and open files.

I have a fork working and submitted to CA, just waiting for it to get approved.

Give me until tomorrow

https://raw.githubusercontent.com/unraid/unraid-tailscale/refs/tags/2025.04.17/plugin/tailscale.plg