EDACerton

The integration needs to update. Part of the API schema changed (one of the risks of the API still being somewhat in beta).

The update posted earlier today should fix the funnel issues on 7.1 and earlier.

It all depends on the hardware. There are two versions of storcli in the plugin: storcli-3404 and storcli-3205 storcli runs build 3404. You could try storcli-3205 and see if that does any better.

It is more complicated than that, and I don't intend to engage this any further than this comment. There was no conflict at the time this plugin was added to CA... the original plugins had been removed by the author, leaving users without any option. I elected to restore the plugins (originally as-is, then adding improvements) so that users would continue having the plugins available despite the actions that were taken. Renaming the plugin now is both complex, and will create confusion for users since it would require renaming the plugin and removing the original one from CA simultaneously (otherwise, it gets blacklisted), which then causes FCP to report the "pre-renamed" version (which everyone has installed) as unknown to CA and therefore potentially suspicious (until the users with it installed update, at which point they could pick up the "renamed" version. Since I didn't create the conflict (there was no conflict when I started), I don't believe that's my problem to fix. If the staff want otherwise, they know how to get in touch with me, I chat with them all the time.

Generally, problems with plugin installation end up being related to your network settings. What happens if you run the command I provided?

It sounds like Tailscale isn't downloading correctly. What do you get if you run this from a terminal? wget https://pkgs.tailscale.com/stable/tailscale_1.86.2_amd64.tgz

As long as you’re on Unraid 7, it should show up in apps.

@ljm42 Can I get permission to use snippets from here as examples in https://github.com/dkaser/unraid-plugin-template ? (Of note is that the repo uses the Unlicense/public domain so that it can’t place any restrictions on projects using it.)

I have https://github.com/dkaser/unraid-plugin-template , which could be a starting point for this. It seems like it would just need some additions to Sample.page to include some extra things.

I intend to keep this around. It's been substantially improved compared to the original version, and dlandon also applied restrictive licensing (so, if he were to remove them again, no one would be able to fork it like I did).

The plugin and the "Use Tailscale" option are actually two completely separate things, the plugin doesn't provide any of the "Use Tailscale" functionality. (In fact, I generally recommend against using it for a variety of reasons related to how it operates.) For support with it, just make a topic in the overarching "Tailscale" forum: https://forums.unraid.net/forum/111-tailscale/

Ah, I see what's happening. The check that is supposed to start with 7.2 is already running, but you won't see the option that controls it until you update. I'll send you a PM with a fix in the meantime (it's simple, but I don't want to post here so that folks don't try it blindly).

Did you install the 7.2 beta? There's new logic/options around funnel that turns on in 7.2.

You should be able to open the container console and do whatever you need to, but this isn't the support thread for that functionality. If it involves "Use Tailscale", you should make a separate post for that. This thread is only for the plugin (Settings->Tailscale in the WebGUI).

The plugin doesn’t interact with the “Use Tailscale” option in containers, they are two separate systems.

I wouldn’t put the effort I do into the plugin if I thought the backend was unreliable. I can also void your guarantee right off the bat since I run Tailscale across a plethora of platforms, update regularly, and don’t have issues at all. It’s fine to move on, but the thread needs to now as well.

This is a support thread, not a complaint thread. There are many folks who run Tailscale on many devices without issue. It’s a good platform and I intended to continue using/supporting it. Your standard of “I can’t run something that only works sometimes” is unachievable, too… every computer system has bugs, whether that be hardware (that can fail), operating systems (which can fail), or software (which can fail). Even Unraid itself has had its fair share of issues that would break that standard. You don’t want Tailscale, that’s fine, but that’s off topic here.

The SIO guide that gives those instructions is out of date, and (if you look in the comments), turning Tailscale DNS on is a bad idea for most installations. From your diagnostics, the only devices on your tailnet are the server itself, and an iOS device which shows as offline. What are you using to test with?

I looked at the diagnostics, and I don’t see any problems with br0… it’s still there and working, so I’m not sure what problem your seeing. I’d recommend restarting the server, the plugin update also restarts the WebGUI, so it’s possible there was some other issue that the restart brought to the surface. You might have to log in to Tailscale again after that — it looks like you tried the reauthenticate button a couple times, which instantly expires the node.

Please provide plugin diagnostics following the instructions in the pinned post: https://edac.dev/unraid/plugin-diagnostics/usage/

What version of Tailscale do you have on the Mac? The latest version (1.86.0) had issues on Mac and got pulled.

I can probably work something in :)

I've been using that workflow for all of my plugins for a while, but just turned it into an action so other folks could benefit from it :)

I have a Github Action that takes care of all of that stuff for me :) GitHubRelease Unraid Plugin - GitHub MarketplaceBuilds and releases an Unraid plugin from a GitHub repository

The filters need to target the disk* folders, not /mnt/user (since that's not actually a disk). Here are some alternate filters that would work, from broadest to narrowest: /frigate-recordings/ (filters out anything in a frigate-recordings folder, on any disk) /mnt/[^/]*/frigate-recordings/ (matches anything in /mnt/*/frigate-recordings) /mnt/disk[[:digit:]]*/frigate-recordings/ (matches anything in /mnt/disk#/frigate-recordings/)