• Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About ksarnelli

  • Rank


  • Gender

Recent Profile Visitors

1020 profile views
  1. How did you create a hidden share on Windows without a $ sign? I'm not doing any drive level sharing, just regular user shares.
  2. Just for my own sanity, I made the changes I described above, recreated the package archive and deployed it. Everything works fine. I'm able to add $ shares, access them, delete them. The online status remained connected and I was able to delete the $ share without affecting any of my other SMB mounts. If you want me to send lib.php I will happily send it over (and obviously UnassignedDevices.php needed to be modified to remove the $ check as well). Otherwise I guess my course of action will be to just script these changes every time a new version of unassigned devices is relea
  3. Who said the shares aren't secure? It's about keeping the share list tidy. No need to show users shares that aren't for users.
  4. It's obviously your decision since you put in all of the work for the plugin, but I don't really think it's an edge case. Using a trailing $ is the only way to hide shares on a Windows server, and I've seen hundreds (if not thousands) of uses in the wild. Usually to reduce the number of visible shares when a server has shares intended for users and others intended for automated processes. When I tested the code change above I was only testing that one particular function (get_samba_mounts), but after looking at more code I'm pretty sure the other issues you encountered were from
  5. How do you mount an SMB share that contains a $ character (a hidden share running on Windows)? When I try to add the share using unassigned devices it fails with the following error in the log: unassigned.devices: Share '//blah/blah$' contains a '$' character.#011It cannot be added. I tried manually adding it to samba_mount.cfg, but it still doesn't work there either. Adding some keywords because this issue is hard to search for: dollar sign EDIT: I found an old chain about this issue from 2016 where @dlandon incorrectly believed that 'mou
  6. Bring up the edit page for the container and change the repository from "binhex/arch-qbittorrentvpn" to "binhex/arch-qbittorrentvpn:4.2.1-1-05". By default the "latest" tag is pulled unless you specify a tag in the repository field.
  7. Same issue here. I reverted to the 4.2.1-1-05 tag for now.
  8. This is exactly the issue I was seeing - I was able to get it working in GUI mode by disabling/re-enabling bonding *and* bridging, but upon rebooting into normal (console) mode it wouldn't work again. Still have not had a chance to investigate further, but just wanted to make sure I noted it here. The only difference is that I'm using an older Supermicro board (an X8DTN). In the meantime I disabled LAG on my switch and in unraid.
  9. Thanks - next time I have a chance I will do that and post to general support as you requested.
  10. Apparently we weren't the only ones, I found this thread: As far as adding diagnostics it's not that simple without a network connection and the only access being a console via IPMI. I'm pretty sure it has something with bonding+bridging but I didn't have time to continue experimenting and finally just disabled bonding in unRAID and disabled the LAG on my switch to get the server running again. Not sure when I will have time to troubleshoot further.
  11. I just upgraded from 6.7.2 to 6.8.0. I have link aggregation configured using 802.3ad and after the upgrade my unraid server was no longer accessible from my network. I accessed the console through IPMI and can see that br0 has a reserved IP in the 169.254.X.X range, indicating that it couldn't contact the DHCP server. Already tried rebooting again. Everything was working (for years) before the upgrade. Any ideas?
  12. Updated the container this morning and now getting: nginx: [emerg] dlopen() "/var/lib/nginx/modules/ngx_stream_geoip2_module.so" failed (Error loading shared library /var/lib/nginx/modules/ngx_stream_geoip2_module.so: No such file or directory) in /etc/nginx/modules/stream_geoip2.conf:1 Checked and the module is in fact missing. Any ideas?
  13. I guess that's what I'm going to have to do too. I don't like running containers in host mode unless they have dedicated IP. It's just weird because I had zero issues for years with the old container, and immediately had issues when I switched to the new one.
  14. I have the exact same issue after switching to the new container (using the 5.9 branch). Did you ever find a solution?
  15. Looks like this plugin breaks when an unassigned drive is passed through to a VM. Getting lots of PHP errors after saving. Hopefully you can get it to work. Really like this plugin over the alternatives. Thanks!