Darksurf

This actually shouldn't be too difficult? Wireguard could run on the host and connect to a bridge you setup on the host, then connect all your dockers to that specific bridge. IIRC SpaceInvaderone shows you how to add a "proxynet" docker network (bridge) on youtube. Then you could possibly setup one wireguard tunnel to lead to that bridge? This is all in theory, I've not personally tried this.

So just an update, I'm currently stuck between a rock and a hard place. I can switch to Unraid 6.9-rc1 and have no hardware transcoding OR I can stay on 6.8.3 and keep hardware transcoding for my Plex Docker, but lose the ability to monitor temps, efficient VMs, etc.

I just wanted to thank Limetech for getting Unraid 6.9-rc1 out with the 5.5 Kernel. Thanks guys, I really do appreciate it. This should get me going without much issue. The only part I lack is the CPU itself and I plan to order it in the next couple of weeks so this really smooths out my server transition. I'll update with what support looks like after the server switch. Thanks again.

I don't plan on overclocking. The CPU is plenty beefy by default. I do plan to "OC" memory but I don't see 2933mhz on unbuffered ECC as pushing my luck. I avoid gigabyte like the plague after running though a BIOS bug that would hardlock the system (even in the BIOS before reaching the OS!) Using a configuration they claimed to support and they blamed it on the fact that I use Linux and refused to support me. Even after explaining it locked up without even reaching an OS, they finally relented but claimed their bench test station doesn't have the hardware they claimed to support so they couldn't test. They basically left me hanging and kept claiming it was Linux so they could close the case. The specific scenario was using a specific AMD APU with 2400mhz DDR3 with the GPU set to 2G instead of 1G. They aren't Linux supporters and they suck when it comes to my experience with them. I'm normally an AMDGPU user, but my Unraid server uses a GTX 1050Ti for video transcoding in my Plex docker. It's my only Nvidia GPU.

I dunno, the reviews claim its a decent linux workstation board, albeit with an issue with the sound card possibly fixed in newer kernels? I've had pretty good luck with ASRock. Even my Desktop uses the ASRock Phantom Gaming ITX X570. I've used ASRock Rack boards in the past too without issue. Wendell with LVL1Techs did a review and decided it was a decent board, especially for the money. He said the VRM heatsink actually did pretty well and the VRM may only be 8-phase, but it was high quality. The Fan can be loud, but it's going to be in a server chassis in a rack so I'm not really worried about that. The VRM is sufficiently cooled to even during overclock. Cinebench, Blender,, and even 7zip Benchmarks all showed the same Scores as all the other boards. There was no real difference outside of margin of error and ECC memory works and is supported by the board. What's not to like? It's perfect and affordable for my situation.

Thanks, I need QEMU for this server to even work. No point in me having a 32-core 64-thread server if VMs are a no-go... I guess I just need to find a solution to get a 5.4+ kernel and have Nvidia card support? Sounds like a steep request considering unraid is very much like a "live distro". Guess I'll have to look into solutions for the 5.x kernel problem?

I'm looking to upgrade my server to the next level. I need a beefier VM for Sabayon Linux Development. Due to this I'm looking at throwing a lot of money into a Threadripper 3960X 24 core or 3970X 32 core. I'm also looking at the ASRock sTRX40 Creator board. Will unraid support this? I know for much of Ryzen stuff (especially Threadripper) 5.4+ kernel is recommended. The 2 NICs could also be an issue with older kernels.. https://www.asrock.com/mb/AMD/TRX40%20Creator/ 1 x 10 Gigabit LAN 100/1000/2500/5000/10000 Mb/s (AQUANTIA® AQC107): 1 x 2.5 Gigabit LAN 10/100/1000/2500 Mb/s (Dragon RTL8125AG):

Is there an ETA on a 5.4 LTS kernel? I need it for the threadripper server I'm building with an ASRock sTRX40 Creator MB. My current 8-core Xeon is doing OK, but I plan on needing a beefier chip in the near future as I'm hosting a VM for a Linux distro build server.

Excellent! How hard would it be to get this package added to nerd tools plugin I wonder? Thanks for the assistance!

So evidently there are 2 versions of the rename command. Besides this being utterly terrible, the one packaged with unraid comes from util-linux and sadly doesn't support regex as far as i can tell. I'd like to know if unraid can ditch the rename command from util-linux and replace it with the more capable Perl version or maybe give me some instruction on how to do so myself. Thanks, Darksurf

Just upgraded from 6.6.7 using LSI HBA-mode RAID card. LSI Logic / Symbios Logic SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] Everything works great so far. All dockers loaded, VMs running, logs are clean. Great work! It doesn't like edits to the /boot/config/go file. Is it still needed to bump the size of the logs partition? Is there any way to do this via webui configuration yet? darksurf@cold-rewind:/$ cat /boot/config/go #!/bin/bash # Enlarge the LOG partition (because Dynamix System Stats needs at least 186Mb, default LOG is 128Mb) mount -o remount,size=500m /var/log # Start the Management Utility /usr/local/sbin/emhttp -p 80,443 & Thanks again for the hard work guys! 6.7 is working up to be an excellent release!

OK, I just realized the issue. Evidently UNRAID is not aware that proxynet is a bridge. I had to select the default bridge and it then gave me a container port option! After setting the container port option, I was able to set the network interface back to the proxynet bridge and it worked!

having an issue with this docker. I kind of want to blame unraid for this though. All my other dockers are working fine. In fact, this docker is working. The problem is I'm not getting a port mapping from the host to the docker and I can't even specify one completely. You can see in my attachment that I attempt to create a port map, but the options don't give me a place to choose a docker port, only a host port. and if you look in dockers tab, you see there's no mappings meanwhile the other dockers have no issues.

OMG thank you!

Sorry guys, didn't mean to cause you trouble, I evidently caught the flu right not long after that tweak. I had intentions to go back and fix that, but flu hit me pretty hard, I'm at the end of it now. Seems like you guys got it under control! Thanks for the fix and sorry for the trouble.

Interesting, its still setting the directory as 770?, just performed uninstall and reinstall I even went back and removed cache to make sure it wasn't using an old script. I've updated the plg again with a few lines to automagically change the folder perms after install so no additional script-fu is needed. I noticed other plugins were using this method so I'm trying the same. https://github.com/docgyver/unraid-v6-plugins/pull/3 https://github.com/docgyver/unraid-v6-plugins/pull/4

If we can get these merged, it'll fix the wrong perms issue. https://github.com/docgyver/unraid-v6-plugins/pull/1 https://github.com/docgyver/unraid-v6-plugins/pull/2

you could try just setting it to use bait files instead of also using bait shares and see if the issue still occurs. I currently use the bait files option with the bait shares option disabled.

When you write files and have a cache drive, the machine will offload those writes to the SSD because its faster, then the mover will force those files off the SSD/cache drive onto the HDD storage. the mover runs on a cron job IIRC to automatically move files from cache to long term storage. Sometimes the system will just add a label to the HDD or the share that they are read only, sadly if you fix the problem and it goes back to R/W that label can still remain. you can manually go into the setting of the drive or share and remove that label. its only meant for you to notice in case of a problem. I use the plugin and I have no issues. I've been using it for a long time now. Plugin works like a boss. Make sure something or someone isn't "organizing" your files by deleting or moving ANY bait files even if they are visible. this will trigger the plugin to go on lockdown.

odd. you can go to the plugin settings, stop the service and click delete all bait, and start the service so it can generate new bait. See if that fixes your issue. the only way there should be false positives is if the bait is going missing. I also don't use bait shares, just bait files.

thanks, I'll give these a try. I actually don't plan to use unraid GUI through forwarding, I was just using it to make a point to show what I was seeing with Lychee where the page isn't rendering properly. I already access unraid GUI through SSH tunnel as a safety measure.

If I were to post screenshots of what I'm seeing, would that help people diagnose my issue and give me some feedback?

sgt_spike you need to edit the "default" file. You can look at the one I have posted previously, but I'll be honest, it doesn't work right for me... I've got PLEX working in reverse proxy and keeweb working as nginx is hosting it, but thats about it... Everything else is broken

I've tried getting unifi passed through (has trouble loading), homeassist (has trouble loading), qbittorrent (502 bad gateway), lychee on apache (loads really big icons on white background out of order), lychee in www folder (Server error: API not found), and unraid has the same issue as if I were handing off to lychee on apache with all white background some text, but no acutal website. I'll be honest, I've never even used nginx before this docker. Any assistance would be extremely helpful. proxy.conf default

I'm currently trying to get lychee working in this docker underneath the www folder and I get "Server error: API not found". Lychee has no issues in apache when accessed locally, but for some reason lychee doesn't want to work correctly when passed over from nginx to apache OR when just using the www folder in letsencrypt. This stuff is literally drag and drop into a www folder and it should work. As for the unraid UI, it seems to completely strip EVERYTHING but some text leaving the page bare and white with some text in one column. Whenever I try to access index.php it just downloads the php file instead of running it. Is there something wrong with this docker when it comes to php? Logs to docker look clean. No errors in log files. whats happening here?