dmindfuse

Not sure if it is still relevant, but you may find inspiration for this effort in the associated issue on github.com. I was trying to assist with this, but it needs someone more skilled in php/nginx to decide what to do with PUID:PGID container runtime ownership. Cheers. PS: an alternative to Movary is Scrob: https://scrob.app . It seems to be newer and runs with Postgresql as a backbone. (not tried it yet)

Well, for every 10 that have no problem there's always 1 that does 🤔. Today that was me. After plugin updates, docker stop, VM stop, array stop, I triggered the installation after clicking on the "Verify" button. It started, but it never came back from "Please keep this screen open while we update some things". I waited for an hour, then logged i [...cut...] I triggered it again. The only active process in top is "node /usr/local/unraid-api/dist/main.js"... while "Please keep this window active...". So, I have yet another sweat outbreak... ℹ️ Note to developers: Add to the upgrade instructions to "Disable Browser Tracker Blockers". In my Vivaldi browser, the update only offered the "Confirm" window after I had selected "No blocking" on the URL. This refreshed and then allowed me to confirm and start the upgrade.

Today I fixed my problem. So, brief recap, in my case the problem existed on the far left on wireguard clients: [wireguard on laptop] -> internet -> [wireguard on openwrt] -> lan -> [unraid host docker container:port] Following some intense online searching and pondering... I wanted to add specifically the route for my wireguard vpn clients via the openwrt router on my unraid host: ip route add 10.20.20.0/24 via 192.168.1.1 RTNETLINK answers: File exists Unraid complains that that route already exists. Looking at my docker networks I realized one was configured with the same subnet as my wireguard vpn clients on openwrt, presumably causing routing issues. The solution: create a docker network using any other subnet than in my case wireguard 10.20.20.0/24, then connect containers to this network instead. From this point, I was able to reach them from my vpn clients. 😮‍💨 One more thing learned. For a network expert this probably 101, but I never knew docker networking has consequences beyond the host. One has to consider the entire network at home, not just on the host.

Hi everyone. Just out of curiosity, are you using the Wireguard packaged with Unraid? I ask, because I run a Wireguard instance on OpenWRT and the routing problem for anything (including the webgui) Unraid related is persistent here too. I cannot access from a VPN network (road warrior), via OpenWRT Wireguard any resources on the Unraid host. I can perfectly access my openWRT webGUI on the same network. The problem is really imposed upon me by Unraid. I have tried serveral things in OpenWRT (masquerading, forwarding...), all to no avail. I also tried on the CLI to add my VPN subnet to the iptables for DOCKER-USER, but this solved nothing: iptables -I DOCKER-USER -s 10.10.10.0/24 -j ACCEPT. Being new to Unraid, I was wondering if anyone could explain the mechanisms behind this blocking and where or how we are supposed to influence it? I find going in via iptables a little bit dark and cumbersome (coz I don't understand it haha). Wish ufw were available, or a GUI. Are we not supposed to manage networking at the firewall layer as Unraid users? That could be worrying, coz I like to think I have control ;). Thanks.

@MAM59 , thanks, no actually. ;) After losing a fair amount of hair I decided to go through the configs one by one and lo and behold, I observed that - for whatever reason - the NTP configuration I thought I saved, was not there. So, my server configured with the right time zone, but wrong clock was running out of sync and I hadn’t noticed it. This caused DHCP to behave unlike what I expected. To be in sync or not to be in sync. So that was one. The other one I hadn’t mentioned, where the dns did not resolve, I solved by removing the static IP and relying on static assignment via dhcp entirely. It seems unraid doesn’t register with dhcp when configured with a static IP… or I might yet have done something else wrong… 😑 Anyway, it’s running now. I’d like to try LACP, but I’m a wee bit scared I re-enter the void 😂.

@MAM59 , thanks for the input. It's a bit more complex still. Even on my desk, after I boot, I get a webGUI, but it seems I can not login after the first successful attempt, which leads me to believe, something is in fact crashing. Normally I would expect a keyboard getting plugged into a USB port to allow me to type away shortly. But in this case, on-screen nothing happens, suggesting the box hung itself up. Tere has to be a simple explanation. For example, the network... this is config it creates is not correct. It creates a bond with 4 nics, but I only have 2 and I only use 1. It activates ipv6 and not ipv4 dhcp, yet it gets a v4 ip... And STP is set to no, even though on unifi switches this is activated. So i tried to manually change the network.cfg, but that only seems to make it freeze up after boot, my guess. Dear me, I hope I can get a refund if this leads nowhere, but I will keep trying a bit more.

Hi everyone. Never in my life have I had such difficulty to get a computer to show up with an IP and connect to it via a browser. Here's what's going on: I plugin a vanilla Unraid on my desk, stick in HDMI, keyboard, boot it. I sign in to the GUI. All good. Network is DHCP, I leave it at that. RJ45 is in port 2. Now I unplug it, move the Unraid to the floor behind me. On the same USW-60 unifi switch and a different cable I plugin port 2 into a different port on the switch. Boot. I see an IP in OpenWRT, but here it comes: I can never reach the webGUI! Only difference here: no keyboard in USB/at all! So, power off, try a different port, or a different cable, or a different port on the switch, same outcome, I see an IP but I cannot reach the GUI. The ports on the Switch all have the same configuration, VLAN 1, as did the port I connected to on my desk. Still no keyboard in USB. Next, I power off, move the Unraid back to my desk, plug it in, get an IP, and boom: I can access the webGUI I have wiped network.cfg and network-rules.cfg countless times to iterate over this in cycles and I for the life of me cannot explain why this is happening. Unfortunately, I have no keyboard and Screen on the floor behind me and not available for a quick and easy move to work out what's going on. I am desperate, I can't explain this. Unifi ports don't show anything wrong. Port configurations aligned and checked to be exactly the same as that 1 port on my desk. Who can tell me what is going on here?

Your hint of ports was all I needed to realize I had the Ethernet jack plugged into the RJ45 COM Port! Wow, this is embarrassing. 🫣 The Etherent ports are right next to that, quite easy to plug in the wrong one, when you turn the device around and work mirrored. Anyway, thanks for your patience... I should've caught this myself though.

Hello all ✌ Completely new to Unraid. I had tried OMV and Rockstor before Unraid. I installed it to USB and booted it in the guest network on my desk. Satisfied with a login page, I configured root password, added pool.ntp.org and then went and unplugged it (no graceful shutdown) and moved it to plug it into my LAN headlessly. Since, it gets an IP, but there's no webGUI reachable on it. I have reset power 20 times over and nothing changes. SSH is not running by default I suppose because I can't reach it. I use a small protectli VP3230 on coreboot. Anyone have any pointers to help me get this show on the road? Am I missing something essential pertaining networking? Is moving it or unplugging the network cable not permitted once it's installed perhaps, which I cannot imagine? It also seems to loose it's IP assignment when I configure a static IP on openWRT with a 5min lease. Unraid was setup with DHCP. So, not a great start, but I'm positive this is all me and not the software 😄. Any do's and don'ts welcome. Thanks everyone