eric.frederich

I just created a Win11 VM and trying to use WSL2 within it. It's my understanding WSL2 uses a real Linux kernel running under Hyper-V (whereas WSL1 was more of a translation layer; like the inverse of WINE). When I launch it, it seems to be working but I get this error in my terminal: wsl: Nested virtualization is not supported on this machine. It seems to be working under WSL 2 though. PS C:\Users\eric> wsl --list -v NAME STATE VERSION * ub24 Running 2 What do I need to do to get rid of this message? Things I've tried These were mainly from Google's Gemini AI. On the Unraid host I verified I got a 1 returned from cat /sys/module/kvm_amd/parameters/nested I've enabled Hyper-V on the Windows guest. On the Unraid VM xml I've added within <cpu> section: <feature policy='require' name='vmx'/> , then later switched vmx to svm I've added within <features> section: <kvm><hidden state='on'/></kvm> Verified that <cpu> had mode='host-passthrough' set. On the Windows VM I've created a .wslconfig file in my home directory with the following contents. [wsl2] nestedVirtualization=true

Thanks... not sure that makes me feel any better though ;-) Thankfully I'm getting a new NAS sometime soon (it's on a slow boat from China). Minisforum N5 NAS Pro with ECC RAM. Mayne this is something ECC RAM would have fixed?

I downloaded an Ubuntu iso file through a binhex-delugevpn app. The resulting download has a single bit flipped. Timeline: Since 2017, there have been 51 parity checks. Only one had any errors in 2017 after an unclean shutdown. All other parity checks have 0 errors. Aug 2nd: parity check (no errors) Aug 13th: iso downloaded via torrent Aug 19th: bit flip noticed after checking against sha256 sum, parity check initiated Aug 20th: parity check finished (no errors) I have resisted clicking "Force Recheck" on the torrent in the deluge UI because I suspect it will notice a bad chunk and correct it. I wanted to leave it in this broken state to come here and ask if there is something else I should try before doing so. Because there are no errors I should assume that this is not bit rot and maybe some other corruption occurred during various moving of the data? Deluge settings for that download: Download folder: /data/incomplete (/mnt/user/download - cache: yes) Move Completed folder: /isos (/mnt/user/isos - cache: yes) So my understanding would be: deluge downloaded the data into a cache enabled volume (/data/incomplete) deluge moved it to another cache enabled volume (/isos) Unraid's mover moved it from the cache to the array I'm not sure at what point deluge verified the torrent. Perhaps after download and before moving? Maybe it doesn't verify the entire checksum but just the chunks?... not sure. Is there anything else I should check? What do you suspect happened? Can I be fairly confident I have no bit rot because there were no parity check errors?

Posting the conversion from IRC in case anyone else is interested in the details or potential stop-gap workarounds.

Somone on Libera #unraid channel suggested changing over to `ghcr.io`. I tried this on my mariadb container. I edited it and set it to `ghcr.io/linuxserver/mariadb`. It pulled the image and started it. When I went to "check for updates" it still says "not available" even now after it's been set to `ghcr.io/linuxserver/mariadb` Would appreciate some help understanding what's going on here. Are there error logs to look at somewhere?

I'm in desperate need to replace my existing aging Unraid server. I'd prefer to go pre-built. Does this N5 or N5 Pro look like a good option? Currently I run mainly Plex, NextCloud, and a torrent client. I'd also like to run a VM or 2. It seems some tech influencers are excited about this but I'm not sure if it's genuine or not. https://nascompares.com/2025/01/08/minisforum-n5-pro-nas-revealed/

All 3 of my lscr.io containers have been saying "not available" when I check for updates. I used the terminal from the web UI to run `docker pull lscr.io/linuxserver/swag` as root and it pulled fine, so it's not a DNS issue. What could be the problem? Why just these 3 (swag, mariadb, nextcloud)? I'm on 6.10.3. I don't want to update right now as I plan on building a new NAS as soon as the Minisforum N5 comes out.

Almost a year ago (Oct 28th 2022), I got hit with some PHP version error. I changed my image to use a fixed tag (linuxserver/nextcloud:24.0.6) and have been using that fine ever since. I feel like I shouldn't be running a year old software though. Is it find to just change it to (linuxserver/nextcloud)... will it upgrade fine?

Just got a new laptop yesterday... what a dumb time for me to update this Docker image. I got hit with a PHP version error. Just changed my tag to "linuxserver/nextcloud:24.0.6" and thankfully it seems to have worked. I didn't get that message about mid-upgrade that someone else got.

I've been unable to download stuff, even things like Ubuntu iso torrents. It'll make some initial connections to a peer or two then nothing. I updated my openvpn config file and crt from IPVanish, nothing. I've used the same openvpn config file and crt in a qtorrentvpn container and it is able to download torrents. No idea what is going on.

Hi. I'm having difficulty running this on anything other than port 8080. The problem is that port 8080 is in use by another container of mine. I had to stop that container to even get this thing to start up. I have changed both Host Port 3 as well as the WEBUI_PORT and I cannot connect to the web ui. I am using the custom network proxynet (as shown in SpaceInvaderOne's YouTube videos) for running behind a SWAG (nginx) LetsEncrypt reverse proxy. Side node: the reason I'm trying this qtorrentvpn is becaues for some reason my deluge container stopped being able to download. I can't even download an Ubuntu ISO torrent. I updated my openvpn config files and crt files. No idea whats going on there. The same config files are working fine here on qtorrent. In my deluge container the torrents seem to start to download then immediately stop. They'll have a peer pop up then disappear.

Cool thanks for the reply. Maybe you can clarify something for me then. It's my understanding that: WireGuard is baked into the Linux kernel TailScale is built on top of WireGuard The Dynamix WireGuard plugin for UnRaid simply provides a web-ui to manage the WireGuard already baked into the kernel. Is all of that correct? If so, I'm curious how they don't conflict with each other.

I currently have WireGuard working with UnRaid via the Dynamix WireGuard plugin. What do I need to do if I want to try out this TailScale? Can both run at the same time or do I need to uninstall the WireGuard plugin? I only have two clients, so I don't care if they're lost.

Awesome work @HyperV thanks. It worked for me. Where is that code maintained? I wanted to see if it was fixed in a newer version of if we should file a bug. All I found was this which seems to be 5 years old and completely out of date. https://github.com/limetech/dynamix The DockerClient.php in that repo doesn't even have any Docker-Content-Digest.

I'm having this issue as well. I'm also on 6.8.3... I haven't updated my images in 2 months. Now every one of them is showing "not available". I hopped on #unraid IRC channel on FreeNode and asked there too. It's pretty quiet there, but the one person who did check was also having the issue... again on 6.8.3 I wouldn't assume it's a problem with this specific version until we hear from someone on a different release saying "it works for me". That hasn't happened yet.

I'm having this problem as well.... I constantly have to `umount` then `mount` the shares after getting stale NFS errors.

Got this working although very slowly. I only have 2 clients on my Zero Tier network. I have this Unraid Docker container, and my cell phone. Browsing files via Total Commander did not work at all (some access denied error). Browsing via CX File Explorer worked but basically unusable due to slowness. Also tried SSH via Juice SSH. Again, basically unusable. It's not my mobile connection because I have a jump host on my network and connecting over internet to Unraid via my jumphost works fine and is fast/responsive. My phone is a Pixel 2. It should bet powerful enough right?

I'm exposing this to internet via the letsencrypt app also running on my Unraid server. I have configured a .htaccess file to enable http basic auth so it's not wide open. I ran into an issue because the name had upper case letters which don't play nice with Docker's DNS. https://stackoverflow.com/questions/55518144/using-variable-in-nginx-conf https://github.com/linuxserver/docker-letsencrypt/issues/287 Perhaps the name should change to gitlab-ce instead of GitLab-CE

Hi, I recently set up my Unraid server to serve some conatiners up over a reverse nginx proxy (see video below). I'm curious whether this GitLab application is safe to expose to the internet via something like "gitlab.mydomain.com". What could/should I do to protect it? I just installed it and signed in once, then created a user. I noticed that anyone could just register and it didn't do any kind of email validation. Is there a way to disable registration? I want to manually create all users, will be just a handful.

Yes, everything you said is understood and correct. On my home network I am able to use plex by the domain address. Same from my phone. It works. What I was asking though, is how to make it possible to access it by ip:port while at home and not have this traffic traverse the public internet. I would like to use my domain when I'm away and my ip while at home. I believe this can be solved 2 different ways. Let plex run on proxynet and either modify template to publish the ports modify the Extra Parameters to include port mappings like -v 32400:32400 Let plex run on host and Hard code Unraid IP address in proxy config: i.e. change "proxy_pass http://$upstream_plex:32400;" to "proxy_pass http://10.10.1.99:32400;" I thought the best way to fix this would be to have the linuxserver guys change their template so that it would play nice with the LetsEncrypt container/configurations which are also owned by them.

This is how I understand how it works for me currently from the internet: plex.mydomain.com has a CNAME record which points to mydomain.duckdns.org which points to my public (mostly static) IP. Then, without getting into specifics of pfsense vs. Unifi, could you explain what it means to "setup DNS resolver". What should my local DNS resolver resolve plex.mydomain.com to? As I understand it while plex is running on the proxynet Docker network it is not accessible at all locally. I do not understand how DNS would solve the fact that it's inaccessible even by IP address.

Yeah. Turns out you don't need to rely on anyone else's infrastructure. If you have any machine on your home network which is accessible via SSH just do something like thid ssh -L 9000:10.10.1.99:80 home-computer Where 10.10.1.99 is the local IP of your Unraid server and home-computer is something you have set up in ~/.ssh/config to connect to your home machine. Then I can just point my browser at http://localhost:9000 and everything seems to work.

See attachment... on a scale of 1 to 10, how bad of an idea is this? This exposes Unraid to the internet which is not normally the case. It adds https but is relying solely on whatever protections are built into Unraid. Seems to work but opening terminal windows (either to host or docker containers) doesn't work. Is there a better way to do this? I looked at Serveo but cannot wrap my head around how there is any security there. I think you're trusting someone else to be a man in the middle. unraid.subdomain.conf.sample

I guess another option is to leave it in host mode and not on proxynet. In that case, instead of using Docker to resolve each other by DNS I could hard code the IP of the unRAID server in the proxy_pass on this line: https://github.com/linuxserver/reverse-proxy-confs/blob/master/plex.subdomain.conf.sample#L33 I am still interested in anything I can do locally via DNS on my USG gateway. I'm fairly new to networking. Also, if I did want to edit those template files what is the supported way to do that? Would I copy the xml and call it custom-plex.xml and make my changes there?

When I have the network for Plex set to "Host" I see these mappings listed. 10.9.81.99:1900/UDP <--> 10.9.81.99:1900 10.9.81.99:32400/TCP <--> 10.9.81.99:32400 10.9.81.99:32400/UDP <--> 10.9.81.99:32400 10.9.81.99:32469/TCP <--> 10.9.81.99:32469 10.9.81.99:32469/UDP <--> 10.9.81.99:32469 10.9.81.99:5353/UDP <--> 10.9.81.99:5353 No clue where this list is comming from? Perhaps something within the Dockerfiles somewhere. I manually set "-p 32400:32400" in the "Extra Parameters" and I was able to connect locally. I have Unify/Ubiquiti equipment. How would I make it so that I could use that domain name inside my network? From outsite my network, that domain name points to my public IP address and I have my USG map port 80 and 443 to my unraid server port 180 and 1443 (because unRAID already uses 80 and 443). This then hits the reverse proxy and goes to the correct Docker. From inside my network if I had plex.mydomain.com resolve to 10.9.81.99 then what would be doing the translation from 80 and 443 to 180 and 1443? I understand that you advise to run in host mode, but isn't that accomplished by defaulting to host mode?