weirdcrap

Members
  • Posts

    446
  • Joined

  • Last visited

Everything posted by weirdcrap

  1. It is still concerning though that LimeTech doesn't seem to have learned a lesson about communicating with the community from the last big kerfuffle that drove @CHBMB away. The community is what makes UnRAID great, and to keep the community around communication and engagement should be a priority IMO. I'm also not going to speculate and get mad over what are currently entirely unconfirmed changes to the licensing model.
  2. Alright so I guess the containers were just kind of borked. I removed them and got a "no such container" error. After reinstalling the containers they both check for updates successfully. Should have tried it sooner but didn't believe anything was wrong with the containers since they were both working correctly.
  3. Hmm ok maybe this is a DNS thing? I kind of forgot I had a second server (I've been keeping it off because its so hot upstairs) so I installed the dockers and they seem to be able to check for updates on this server. I compared the repo URLs and they're the same. Both servers are behind pfsense routers (v2.7.0) with nearly identical configurations. DNS on the routers has the two repo domains cached correctly. EDIT: I forgot I think I patched my docker file manually rather than use the plugin like I thought I did: But this wouldn't persist after a reboot without an entry in my go file or a user script, right? I don't have a script or anything to reapply it so I don't think this is the issue but I could be wrong.
  4. I'm having a bit of trouble figuring out what my issue is as I've rarely had any issues with docker and updating before. The LinuxServer.io SABNZBD container and the plextraktsync container are consistently reporting that update info is not available". I haven't changed anything on my end and the repos still appear to be up and active. I don't really see where UnRAID or docker logs any further details about WHY this information is unavailable so I'm struggling to find troubleshooting resources. Repos are here: https://ghcr.io/taxel/plextraktsync & https://github.com/orgs/linuxserver/packages/container/package/sabnzbd I know this was a widespread issue a few versions ago but afaik that was corrected already. I tried to look for threads from others but my Google-Fu is failing me apparently. node-diagnostics-20230711-1258.zip
  5. It is: That's fine I don't really want or need public shares anyway. I have already read through the document from that thread and my laptop already uses the sane defaults mentioned. SMB1.0 is not installed. I already have my credentials loaded in credential manager and a matching user has existed on the UnRAID box this entire time. I played with the insecure guest login setting under lanman and it made no difference so I've kept it disabled. My home network and sharing settings already use sane security defaults: I did not follow the network neighborhood part of the linked doc because I don't really care if the servers show up in the network window or not. All of my exported shares are set to private so no guest read access is allowed anyway. The issue is that I can't even get a listing of my available shares by going to the server path "\\node" so I don't think this is an authentication issue as I can't even get to the point where I would attempt to open a share. Furthermore trying to access a share path directly results in the same unhelpful error.
  6. Turning up Samba logging produced absolutely zero log entries when trying to access the server. So the issue is clearly that the laptop's requests for shares are never making it across the tunnel for some bizarre reason. EDIT: I tested again with a bootable copy of linux on the laptop and I can access the shares fine outside of Windows so this is 100% a Windows issue, not an issue with the WireGuard tunnel. Am I missing some network setting in Windows that allows cross subnet traffic to work that gets enabled when I activate the WireGuard for Windows client?
  7. I've got a fresh Windows 11 install on a brand new laptop and I cannot access my remote UnRAID server via SMB. I can ping by name/IP and access the web interface for management. I have two servers, one local and one remote but connected to my local LAN by a WireGuard site to site VPN. There is a static route established for the remote subnet in pfsense and other devices (Windows 10, 11, & Linux) can access the remote server shares without issue. I have both server's defined in my host file on the laptop. I get an "unspecified error" 0x80004005 trying to access the remote server by name or IP address. I've been making my way through the Windows issues with UnRAID thread but so far nothing I've tried has helped. I've tried enforcing a minimum SMB setting in the extra config for SMB on the remote server. I've also tried adding my credentials into credential manager for the device. My UnRAID user credentials fully match my laptop credentials (capitalization and all) so I don't think the credential manager thing was necessary but I'm not sure what else to try. All of this works fine from my other Windows computer but it was upgraded from win 10 and its possible I changed other settings to make it work but I don't recall what they are if I did. The linux laptop I have and a bootable copy of ubuntu both can access the server without any mucking about. My wife's Windows laptop also works fine. Now here's the real kicker. thinking maybe something was wrong with my WireGuard tunnel so I connected to my phone hotspot and fired up WireGuard on the laptop and lo and behold it works without changing anything!? So What could be causing this? I checked the network settings on both devices and they match, no additional IP settings specified or anything. Everything is pulling DHCP from my pfsense box. I'm fairly certain this is an SMB issue and not a WireGuard issue but the fact that changing net connections and using the WireGuard for Windows client suggests maybe not? So, why do all my other devices work over the tunnel with no issues and not this one? node-diagnostics-20230604-1551.zip EDIT: I'm going to try and bump the log level in samba once I can find a moment to stop the array. I'm curious if there are requests even hitting the server or if I'm not making it past the router on my side. EDIT2: I forgot to mention I also tried making a public share and setting it public to ensure it wasn't a credential issue. I can't even access public shares.
  8. You can setup a VM in UnRAID or really make a wireguard server on any other device besides directly in the UnRAID OS. I set it up on my site routers and it performs way better than UnRAID ever did.
  9. I've gotten this on and off for years across various versions. It doesn't seem to affect anything for me that I can tell.
  10. The problem is no one seems to be able to definitively pinpoint the cause of the issue. LimeTech is apparently unable to reproduce this in their testing and it seems to be limited to only a small subset of users so it just isn't garnering much attention I think. The more people who find this thread and share their experiences the more likely someone will start to take a more serious look at the problem. The only solution at this time is to just not use UnRAID as a WireGuard server if you want to be able to move large amounts of data quickly.
  11. this fixed Recyclarr and PlexTraktSync for me, thanks!
  12. Just encountered this as well after changing a share's minimum free space. Everything seems to be working, last log message was about winbind but i'm not sure they're related. Dec 25 18:40:35 Node wsdd2[11454]: 'Terminated' signal received. Dec 25 18:40:35 Node winbindd[11458]: [2022/12/25 18:40:35.498412, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Dec 25 18:40:35 Node winbindd[11458]: Got sig[15] terminate (is_parent=1) Dec 25 18:40:35 Node wsdd2[11454]: terminating. Dec 25 18:40:35 Node winbindd[11460]: [2022/12/25 18:40:35.498462, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Dec 25 18:40:35 Node winbindd[11460]: Got sig[15] terminate (is_parent=0) Dec 25 18:40:35 Node winbindd[12972]: [2022/12/25 18:40:35.498567, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Dec 25 18:40:35 Node winbindd[12972]: Got sig[15] terminate (is_parent=0) Dec 25 18:40:37 Node root: Starting Samba: /usr/sbin/smbd -D Dec 25 18:40:37 Node smbd[15089]: [2022/12/25 18:40:37.670343, 0] ../../source3/smbd/server.c:1741(main) Dec 25 18:40:37 Node smbd[15089]: smbd version 4.17.3 started. Dec 25 18:40:37 Node smbd[15089]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Dec 25 18:40:37 Node root: /usr/sbin/wsdd2 -d Dec 25 18:40:37 Node wsdd2[15103]: starting. Dec 25 18:40:37 Node root: /usr/sbin/winbindd -D Dec 25 18:40:37 Node winbindd[15104]: [2022/12/25 18:40:37.722342, 0] ../../source3/winbindd/winbindd.c:1440(main) Dec 25 18:40:37 Node winbindd[15104]: winbindd version 4.17.3 started. Dec 25 18:40:37 Node winbindd[15104]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Dec 25 18:40:37 Node winbindd[15106]: [2022/12/25 18:40:37.724476, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache) Dec 25 18:40:37 Node winbindd[15106]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Dec 25 18:41:52 Node sshd[16971]: Connection from 10.250.0.3 port 57350 on 192.168.20.249 port 22 rdomain "" node-diagnostics-20221225-1845.zip EDIT: and just like that after about 10 minutes its gone. No entries in the logs or anything.... very strange.
  13. Oh yeah it never worked right for me. From the day I set it up it ran like crap. pfSense's implementation works great. Got a Proctectli FW4B at home and a J4125 at the remote site both running pfsense 2.6.0.
  14. All of this seems to have been resolved by putting my own router in. Plugin & docker update checks are 3-4x faster than before. pings to hostname's start faster. I'll keep monitoring for DNS issues but I'm considering this resolved for now. A $100 J4125 box from aliexpress and pfSense CE made a night and day difference over that zyxel.
  15. A final update to this. Unfortunately I had to abandon using UnRAID as the WireGuard server as I couldn't resolve this. This issue coupled with my other issue drove me to invest in putting my own router in front of the remote server. I've now built a site to site WireGuard tunnel between my two routers and everything is working exactly as I would expect it to over the WireGuard tunnel. I'm getting my full speed up to the bandwidth limit I set in the rsync command. So TL;DR is don't expect UnRAID's implementation of WireGuard to be able to move large amounts of data without choking. At least not as of this post, hopefully it can be improved in the future.
  16. This is a GUI bug, the setting applies correctly it just doesn't show right in the GUI. See here:
  17. So is the issue that the GUI just isn't displaying the correct setting? The setting hasn't actually been changed?
  18. From the release notes: This is not just applying to new installations. I upgraded my secondary server and my docker custom network type was changed from macvlan to ipvlan.
  19. despite my UnRAID not being a new install my docker network type was changed from macvlan to ipvlan. It also appears to be changing existing settings:
  20. Yes If you have any spaces in your share name you need to either escape them or wrap the share name in quotes.
  21. I had no problems with the commands above that I can recollect. Just be sure to run FIND before you run FIND & DELETE to make sure you aren't getting anything included you don't want.
  22. Alright, was hoping something more conclusive would be in the log. I'll move it to the back ports outside of the case if i have problems with the other internal header. if it still drops out I'll buy a new flash.
  23. zero issues other than human error and your typical disk problems. This is the first flash related issue or error I believe I've ever had in my entire time using UnRAID. I buy quality flash drives and limit writes to them to avoid this exact type of situation. EDIT: Well this is not entirely true, I had a roof leak in my rental house 3 years ago that got into my server and blew my mobo and flash. This is that replacement flash drive so its only about ~3 years old.
  24. Have you modified the plugin with custom rsync flags (under the settings)? the -m flag would prune empty directories but doesn't appear to be part of the default flags. I've never used the gather before, only scatter and I've never seen this behavior. You could turn up the logging verbosity to full and perform a dry run to look and see what rsync's doing without actually affecting your shares or folder structure.