TBT

Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by TBT

  1. Maybe because @EDACerton also has a life and needs to work on incorporating every new release into the plugin!? And because probably tests are done before launching them to the general public? Sounds a tad bit ungrateful to such a great developer.
  2. This is the support thread for the Tailscale Unraid Plugin, not some general thread. Read the excellent Tailscale documentation https://tailscale.com/kb/1019/subnets and/or go to the Tailscale Subreddit for this.
  3. It is a plugin, not a container. Therefore it runs even before and independently of Docker. You can stop and start the Docker service on the web interface via Tailscale. Especially if you don’t autostart your array (due to encryption), this is the only way to start it from remote.
  4. Fixed with 2023.12.05 Update. Thanks!
  5. Thanks! The update has fixed my H12SSL-NT issue with FANA. Top! Quick fix!
  6. My mainboard: Supermicro H12SSL-NT Gen:12 with fans 1,2,3,4 and A,B After the update from a few days ago, I get the error: FANA (3640 RPM): (fan is not configured!) 3640RPM is full speed and very loud Fans 1-4 work as they should and can be controlled, but no setting I try with FANA has any consequence. The plugin version before did not have this problem. What could be done?
  7. PARTIAL SUCCESS! THIS fixed the SMB connectivity problem for ZEROTIER, but not for Tailscale. Still a very worthy direction to investigate from the plugin creator, probably. Both networks (ZT and TS) are "private" networks and the firewall should be set accordingly. EDIT: Transfers via SMB are quite unstable and tend to stall. Investigating. Netbios ist still on right now.
  8. Can cofirm, this happens with Tailscale and Zerotier as well since 6.12.0. I am on 6.12.2, still not fixed. I have all the mentioned tricks applied, does not work. It is still in there with 6.12.2.
  9. Thanks for helping me. Do you mean disabling netbios on Unraid or the ZT/Tailscale interface of the remote device? Removing it on the remote device did not help. I now have both VPN solutions, both included in "Include listening interfaces", but it still does not work. I really wonder how you got yours to work.
  10. Also for me, with Zerotier: not working with Netbios disabled on the ZT interface. And indeed it worked unchanged with Netbios on on 6.11.5.
  11. [6.12] Upgrade to 6.12 breaks access when using Tailscale - Stable Releases - Unraid and Unraid OS version 6.12.0-rc7 available - Prereleases - Unraid I use Zerotier, same problems as Tailscale. Other protocols work (e.g. FTP, HTTPS), but not SMB over Zerotier. Has worked perfectly on 6.11.X, but not on 6.12 any more. It might be due to that "Interface extra" stuff that was added. I ofc set up the "solution", it brings back other protocols, but no SMB.
  12. Still no fix to SMB not working over VPN / alternative interfaces?
  13. I also have the SMB not working issue with ZeroTier. This seems to be an urgent problem for many, as many seem to use Zerotier, Tailscale, Netbird, Netmaker or others. GUI and FTP work fine, but SMB not.
  14. Thank you very much for your CrushFTP container. I would also kindly ask for a CrushFTP container update, in the meantime 10.4.0 is the most recent version. I noticed that it is possible to internally update the container, the update is gone however, once the container restarts.
  15. Witzig, genau mit dem Thema hab ich mich auch unabhängig von diesem Thread auseinandergesetzt und bin erst nach Einkauf und Verbau genau dieses U-56n 8GB Sticks auf den Thread gestoßen. Das Ding ist anscheinend rund 175x so haltbar wie ein Samsung Bar Plus (wenn man dem Video von Spaceinvader One folgt), der nur 29 volle Schreib- und Lesevorgänge überlebt hat (< 1 TBW). Der U-500k wäre nochmals DEUTLICH langlebiger, aber ich bin auch auf den Trichter gekommen, dass diese Verbesserung nicht den Preis von 200€ wert ist und denke dass man mit einem U56n extrem gut bedient sein wird. Der Umstieg mit dem Creator Tool ist leicht, die Sticks haben alle eine eindeutige GUID, so dass die Registrierung des Keys keine Probleme darstellt. Ich habe das auch mal für die englischsprachige / internationale Community ausführlich zusammengefasst:
  16. Dear ChatNoir, I am aware of those entries and do use them and they do work for all drives. I however wanted to have that important info a little bit more on top. Other data could be in there of course as well. Regardless of what information users would want to save there, it should also work on parity drives (as it does with all other drives). That is why I filed the bug report, as it seems to be one (if indeed minor). As mentioned above, I also think that the help fields do have the wrong content in them, as the text makes no sense at that position. It is only with shares that this text would make sense.
  17. I wanted to write my warranty date into every hard disks comment. This worked everywhere, but not with the parity disks. Steps to reproduce: Go to individual parity or parity 2 settings page (click on "Parity" from "Main") Write something into the "Comments:" field Apply Bug: The comment will not be saved, the entered text will disappear. Desired behaviour: The comment should be saved. Possible bug / maybe wrong text reuse: In addition to that, the "?" (help) text in the blue box after clicking on "Comments:" is: "This text will appear under the Comments column for the share in Windows Explorer. Enter anything you like, up to 256 characters." The parity / parity 2 individual drives have nothing to to with any share and certainly do not appear as one. I am not sure if the help box "This text will appear under the Comments column for the share in Windows Explorer. Enter anything you like, up to 256 characters." with any other singluar hard drive makes sense. One drive COULD be a singular share, but mostly isn't.