steve1977

Thanks. The first link doesn't address my issue? Aware of the issues with diskshares and this is what probably led to my duplicates above (and the corrupt 0kb files). I just need to clean it up and then disable the diskshares. Dupeguru may be the way to try it out?

I realized that I have a fair bit of files that exist on two disks, but show up only as one one file on the usershare. Dupeguru does not cover this usecase, so I am looking for help how to fix this. Let me describe the four issues I am facing: Issue #1 /disk1/movies/movie1/movie1.mkv /disk2/movies/movie1/movie1.mkv [100% identical] Issue #2 /disk1/movies/movie1/movie1.mkv /disk2/movies/movie1/post.jpg [metadata for movie1 ended up on disk2] Issue #3 /disk1/movies/movie1/movie1.mkv /disk2/movies/movie1/ [empty folder] Issue #4 /disk1/movies/movie1/movie1.mkv /disk2/movies/movie1/movie1.mkv [0kb file] Thanks for any thoughts and pointers.

Excellent. Thank you! Can you remind what I need to do to access dockers remotely. Something with subnets, but I forgot what. Is there a guide? Thanks!

Thanks for updating the plugin and allow it to select the exit node natively from the plugin as well as the feature to "allow lan". Any chance to make the exit-node description a bit better? For those from Mullvad-VPN, it show the short version rather than the country name. Also, Mullvad is not all together, but mixed with the other. The prior implementaiont (pre-upgrade) was much better and also even allowed to search (e.g., I could search for Miami and then the Mullvad-VPN for Miami came up). Thanks for considering!

I noticed there are a few users having issues since the upgrade to Unraid 7. I am one of them, but my issue seems different, so I am opening a new thread. All works well as long as I use the browser-internal VM Console (VNC). Having some issues when using Remote Desktop. Connects, but somehow gets "stuck" on the user log-in screen (frozen screen). I need to try connecting 5-6 times and eventually it succeeds and I can use it. A bit hard to replicate, but it happens frequently, so it is sufficient inconvenience to report it. I've been using this VM for many years on Unraid 6.x.x and this issue never appeared. Below my VM settings, which may help for troubleshooting? * 4 cores assigned to the VM * 18GB initial and max memory * Q35-9.1, OVMF-TPM, enable-usb-boot=no, hyper-v=yes, usb=2.0 (ehci) * Primary vdisk=virtio, bootorder=1, discard=ignore(no trim) * Sharemode=virtiofsmode * Graphiccard=virtual, mutlifunction=off *VMcontrol=VNC, VMconsole-copy=no, VMconsole-autoport=yes, QXL(best) * Network-br0, virtio-net * Timersource=no/yes/no/no * None/none/none/none

This solved it, thanks!

Thank you. Let me give this a shot and see whether it solves the issue. Is this change "permanent" or do I need to do it upon each docker restart? Or once updating the plugin? Talking about update, I did use the plugin update from your github. Do I need to / can I switch back? How?

I've been doing this now. I put sabnzbd on ita own IP (through br0). Unfortunately, the other dockers can no longer access it? Do I need to set somewhere the option "enable local LAN" in the plugin? Or something else that prevents this from working?

Unfortunately not. I received this in the past (when keeping the plugin activated). I may face some broader network issue, which may well be unrelated to Tailscale (but surfaces). Since I made network changes, my Plex container is now also broken (which has never been exposed to TS), so I must have some other unrelated annoying network issue...

Just disabled the plugin. Enabled within the container. In the log, I am seeing below: Executing Unraid Docker Hook for Tailscale Detecting Package Manager... Detected Alpine Package Keeper! Installing packages... Please wait... Stays likes this forever... Let me wait to see whether there is eventually an error message / time-out message.

One clarification: It downloads within the docker as long as the plugin is active. I need to double-check, but likely it works as long as I go through the exit plugin node. Once I turn off the plugin, it no longer works from within the docker.

An error occurred trying to play "xxx". Error code: s1001 (Network) Using Plex in Unraid docker container. Everything was running smoothly. Since a week, all newly added episodes give me above error. Movies and older TV episodes seem to work. Tried plex-web and device players. Any idea?

Thanks again for your help. I have some time again to play around and try to get it to work. Context: No more Unifi devices. I use an OpenWRT mini-pc as Router together with Asus Zenwifi devices throughout the house. Tailscale plugin works with and without using an exit node. I cannot get the docker-internal implemenation of Tailscale to work if I disable the plugin. Reason is that the docker cannot download/install tailscale within the docker. I checked the information you asked me above: Tailscale health: This is an unstable version of Tailscale meant for testing and development purposes. Please report any issues to Tailscale. Some peers are advertising routes but --accept-routes is false. Accept Routes: No Accept DNS: Yes Thanks for any thoughts you may have. Happy to provide more logs or information as needed.

Thanks. it should be unrelated to my settings. Once i turn off the plugin, i cannot even install TS inside the container. As you say, it is likely related to my home network. For now, i just use the plugin, which works very well and serves 80% of my needs. I may do some changes to my home network, which hopefully will resolve the issue. I’ll revert in a few weeks.

Mmh... Guess that's the issue. I can acccess both URL... I guess the only solution is to change my routers?

Thanks for your help. Hope you haven't yet started. I realized that my issue is of totally different nature. I did some more trouble-shootingl. The issue is that something blocks the TS download within the docker. The package. Likely my ISP doesn't like whereever it is hosted. This wasn't obvious before as I use an exit-node with the plugin. So as long as the docker goes through the plugin-exit-node, all is good and it downlaods. Once I move the docker to br0, it in fact fails to download the TS implementation from within the docker. What I don't understand is why I cannot download TS within the docker. I can access the TS web-site. Also, I can download the TS-plugin without any issue. Do you where the TS package is hosted that gets download from within the container?

Thanks for offering help. Let me elaborate what I am trying to do with specific example. One premise is that I won't be able to install TS on all devices in my local network, so would love to be able to access Unraid UI and dockers throught the local-LAN IP (not the TS IP). There are various things that I am trying to accomplish, but let me start with something easy. Once this works, everything else may also work: 1) TS-plugin with exit node. Unraid GUI can be accessed with local IP (from TS- and non-TS-devices) with local IP. And with TS-IP from remote TS-devices. [this works very well now] 2) Prowlarr docker container that is not routed through an exit-node, but has TS enabled within docker container. Accessible via local-IP from home network. Ideally also via TS-IP for remote TS-devices. [I tried. I need to use br0 to access the docker via local-IP. But it seems that the Internet is not working once TS is enabled within the container]

Thanks. I am starting to realize that I will need both the plugin and the docker-based implementation. And putting some dockers on br0 is probably what I need to do to accomplish this. 1) Console and some dockers - on bridge, plugin-based TS, plug-in based exit node 2) Other dockers - br0, docker-based TS, no exit node 3) Other dockers - br0 docker-based TS, docker-based exit node Ideally, I can still access all dockers from the Unraid GUI when remote. Would this work? I would need to include and exclude some IPs from subnet? I am posting in parallel in the docker-related thread how to get the br0 implementation work (seems complex).

Thanks. This has been helpful. Basically, I'd need to set my docker up with their own local IPs (custom br0). Drawback is that I can no longer access the dockers remotely with TS (plugin) from the Unraid GUI, but could do so via their dedicated IPs. However, in my home network, this should work. At least in theory... I still can't get it to work to access dockers from local-IP (custom br0). To keep things simple, I kept exit nodes disabled (no / none). Userspacing is disabled, so is SSH. Tailscale serve is set to "serve". Any idea what I am missing? ***update*** It works once I set tailscale-serve to "none". Assume this restricts functionality though? ***update2*** It works with "none", but no longer access to the Internet. Do I need to figure out how to add a cert to the container? Seems fairly complex for what I would have hope is a simple thing?

I was referring to this issue: https://github.com/tailscale/tailscale/issues/14372, which has been solved / closed. It is about exit nodes, which are working again. It impacted the plugin. Not sure it also impacted the docker. I am still undecided whether I will use the plugin or the docker implementation. Currently exploring both. What I like about the docker implementation is that I can have some dockers outside TS, some dockers using exit node #1, and other dockers using exit node #2. That's quite neat. Ideally, I would use both (plugin and docker), but not sure they play nice together. Not clear what you are referring to above? LAN-access is critical for me. Most of my dockers are in host-mode/ Are you saying that LAN-access will no longer work if I run TS within the docker?

Thanks. Could i exempt one docker from tailscale and would this exempt also the traffic?

Great the exit node feature is yet again working. I have one question: I would like 2 containers not to use the exit node (Plex and SABnzbd). Is this possible to exclude these two dockers being routed through the Exit node? Or is it all or nothing with the plugin?

I’m talking about both I have the plugin running and it works well. I now like to use the toggle to use a different exit node than used by the plugin. And/or use the toggle not to go through the plugin exit node.

It seems the issue is resolved. Is there also a fix for Unraid required to make docker-based implementation work?

I am currently using the plugin as I want my Unraid console using an exit node. Ideally, I would like to use some dockers not using exit nodes or using a different one. Would this be possible?