thinkscotty

Nevermind. I figured it out. I don't know why but I had to create the static route I never had to use in the past. Left here for anyone else looking for a solution.\

I've encountered several other people on Discord having the same issue, and it's possible it's a bug with 6.10, but I wanted to ensure it's not just me doing something wrong first. I've used "Remote Access to LAN" via Wireguard since the feature was introduced, and I've never had a problem, it's been a magic pushbutton feature for me. I use the feature only occasionally, so there had been a couple changes to my server that could have broken it. The most obvious is that I upgraded to 6.10 (.1, .2, and now .3), but I also got rid of a lot of drives and consolidated to some larger drives and upgraded the server motherboard. I wouldn't think the hardware changes would matter but I thought I'd mention it. I'm running Unifi networking through a UDM Pro. I have a simple network setup with no VLANs, all devices are on 192.168.1.X, including the server. I've used the same Unifi network for a while and Remote Access to LAN worked before. I've had to set up the static routing for NAT or whatever before to make it work, so I don't know why that would have changed now. Here's what I've tried: Checked the Wireguard setup for errors and deleted and re-created the Wireguard tunnel and peers several times. I test it using Wireguard on my iPhone with the wifi off to access from outside the network, set up via QR code. Ensured the DuckDNS is working Ensured that 51280 is forwarded in Unifi Asked around on Discord for similar problems (2 other people have encountered similar problems recently) I don't know what logs I'd need to post for you for this, but if there are any I'd be happy to do so. Ive attached the Wireguard config screenshot here.

I've been happily using Unraid for a while now. I finally got around to migrating my files to Nextcloud. I followed spaceinvaderone's tutorial to the letter but I'm ending up with a page that looks like this when I go to access it from outside the network. The resulting page says "welcome to our server', the exact same landing page you get when clicking the "WebUI" option on the LetsEncrypt docker application. The LetsEncrypt log shows the server ready, and no errors. I'm using a personal web address and have created a cname pointing at a DuckDNS address, which points at my home network. I get the same result if I just directly type in the DuckDNS address, so I don't think the problem lies with my DNS configuration. I suspect it's possibly in the configuration files I had to change, although I can't find where. Or somewhere in the docker user subnetwork I had I had to create. But I can't seem to find any specific post that shows the same problems I'm having so I thought I'd reach out for help. If anyone has a guess at where I might need to look, I'd be very thankful.

What does disturbed connections mean, and how could I go about solving it? I'll post a new diagnostics file here. It's strange though, because my server is showing an up-time of 15 hours. Maybe I uploaded an earlier file. I'll re-download and post here anyway. Thanks! tower-diagnostics-20180512-0824(1).zip

I have 4 WD Red drives, 2 in the array and 2 as parity (I don't need the space but had the drives, thought I might as well have a second parity). Anyway, the second parity drive was just installed last night. I have a nice Samsung 960 EVO SSD as cache, and I usually get 80-90 MBPS upload. I'm currently getting 15-20 MBPS and I can't figure out why. The parity isn't checking anymore and I don't see any other processes going on that would slow it down that drastically. But I'm no expert and easily could have missed something. I have no ethernet connection from my PC to the server, it's all over wifi - but I have powerful 4x4 wifi on both the PC (a dedicated card and antenna) and the router and the wifi speed has never been my bottleneck. So I don't think that's the problem, though I could be wrong. I've posted diagnostics, and any help would be much appreciated! tower-diagnostics-20180512-0656.zip EDIT: SEE NEW DIAGNOSTICS FURTHER DOWN

Here are diagnostics. I'm not sure if they're the right ones or not. I couldn't get the CLI to come up on my monitor, so I was typing into it blind hoping to generate the diagnostics file. I can't be sure these aren't from earlier. But I hope they're helpful. tower-diagnostics-20180426-0511.zip

I replaced my old Unraid server with a brand new one a couple of days back. Every few hours it seems to get disconnected from my network. I can no longer log in to the Web UI or connect to the share on my PC. The only way to fix it is to restart the physical machine. I never experienced this problem on my old UNRAID server so it's annoying and concerning. I have assigned it a static IP via my router. I can't find any support for this in the forums so far. I can post logs or whatever, though I've never done it before so I need to figure that out first. Anyone else dealt with a similar issue? The only thing I run on it is the standard Plex docker app. It's 100% new hardware, except for 2 of the 4 hard drives. Even the USB drive and the license key is new, as I plan to use the old server at work. Hardware: AMD Ryzen 1600 CPU, ASROCK AB-350M motherboard, 8 GB Crucial 2133 DDR4, Samsung 860 EVO cache drive, 4x 3TB WD Red HDD, MSI GT 710 GPU, Corsair CX 550M PSU. I have running off a UPS.