Leaderboard

Oh my god, deleting the cache did it. Thank you and sorry for that...

Finally, with all my cables I get the same results (hope this is clear) (disregard the HDD, I just use it to have contact) :

Beta series is now over. Uninstall the beta CA, and reinstall the production version. Beta series will not receive any further updates.

Thanks for the info. I just changed the double-take xml to make the /.storage folder persistent for easy backup in unraid.

You just need to copy the "URL for Antennas" link into plex manual config and then click connect:

I would suggest you buy another reverse cable and try. Do you have another reverse cable ?? If haven't : Seems you have electronic knowledge, you can plug the forward cable in SFF8087, check the SATA plug port 1 either data pin short to blackplane SATA_1 port which data pin, then do the same thing with reverse cable, if both pin also in short then the reverse cable would be problem. ** edit : due to capacitor in the path, you must test ahead the capacitor, I hope you understand what I mean and the test purpose **

Und es wäre wirklich so schlim wenn du einen Ordner mehr mit "Musik" bei deinen Shares hast? Du könntest den Ordner für andere Benutzer verstecken oder was auch noch eine Möglichkeit wäre wenn du ihn nicht bei den Shares sehen willst ist das du ihn als "hidden" exportierst, dann wird er nicht angezeigt aber er wird dennoch exportiert aber du musst dann manuell zB von Windows mit "\\DEINSERVERNAME\Musik" dort hin navigieren um ihn von SMB aus zu erreichen.

A good reason to be using the Parity Check Tuning plugin so the check runs in increments outside prime time. The length of checks with modern large drives was one of the main reasons the plugin was developed in the first place.

I didn't realize that is what I put in the docs. Last, First should work fine. It should even work with multiple authors in Last, First format. Let me know if you have trouble with that. The github issues page is where most of the discussion on features/bugs is happening right now. As well as github discussion page.

Wow, this is sweet! And exactly what I have been looking for! Quick question, your docs say you have to have the Author as the top folder, but as <First> <Last>, all of mine are <Last>, <First>. I am guessing I have to rename all of them for this to work then? If so, have you considered tweaking it so that both could work?

More info on TPM and Windows 11 for 6.10 :

Hey im currently running version 5.9.29 and is looking to upgrade. Which version would you recommend in terms of features and stability?

Hi @PeteAsking thank you very much, that was exactly the right command I needed. Now I've got to find out how to switch the devices from my old Proxmox/LXC setup to my new UNRAID/Docker setup. 😀 May I ask you if UNRAID will still offer me Docher/Unifi updates or will this setting now stay at version 6.2.25?

I figured it out: I had to reboot after naming server in 'Settings -> Identification'. I had the 'Settings -> SMB Settings -> Active Directory Settings' wrong: Here the 'AD short domain name' refers to the 'my' in 'my.domain.name'. Hope this helps if anyone else runs into it.

It is possible to setup a LAN to LAN VPN connection between two Unraid systems running Wireguard. The steps below should work on simple networks, if yours is more complicated then you'll need to figure out how to adapt it. This assumes you already have at least one working WireGuard connection and are familiar with how it works. First, gather the following information for your two networks. The names and numbers below are samples, you'll need to adjust for your situation: Network1: 192.168.1.0/24 Router1: 192.168.1.1 Unraid1: 192.168.1.50 Endpoint1 DNS: network1.duckdns.org Endpoint1 Port: 52001 Network2: 192.168.2.0/24 Router2: 192.168.2.1 Unraid2: 192.168.2.50 Endpoint2 DNS: network2.duckdns.org Endpoint2 Port: 52002 VPN Tunnel: 10.252.100.0/24 Unraid1 tunnel IP: 10.252.100.1 Unraid2 tunnel IP: 10.252.100.2 A few things: Note that Network1 and Network2 *have* to be different. For instance, you can't connect two networks that both use the 192.168.0.0/24 subnet. You also need to pick a VPN Tunnel subnet that is not being used on either network, it must be unique. You need to setup DDNS for both networks as well. LSIO has a nice Duck DNS docker you can use if needed. On Unraid1: Create a new Tunnel named "Network1-Network2". Don't add a peer to an existing tunnel, it is better if this is a separate tunnel so you can easily turn it off without affecting your other WireGuard connections. Switch to Advanced Mode Click "Generate Keypair". These are the private and public keys for Unraid1, you will need them later. Set the "local tunnel network pool" to the "VPN Tunnel" you chose above Set the "local tunnel address" to the "Unraid1 tunnel IP" from above Set the "Local endpoint" to the "Endpoint1 DNS" and "Endpoint1 Port" defined above Click Apply Click Add Peer Name it "Unraid2" Choose "LAN to LAN access" Click "Generate Keypair". These are the private and public keys for Unraid2, you will need them later. Click "Generate Key". This is the preshared key, you will need it later. Set the "Peer tunnel address" to the "Unraid2 tunnel IP" defined above Set the "Peer endpoint" to the "Endpoint2 DNS" and "Endpoint2 Port" defined above Set "Peer allowed IPs" to the "VPN Tunnel" and "Network2" defined above, with a comma between. i.e. "10.252.100.0/24, 192.168.2.0/24" Click Apply Start the Tunnel On Router1: If UPnP is disabled, setup a port forward for "Endpoint1 Port" (UDP) that points to "Unraid1" Setup a static route for all of "Network2" that is routed through "Unraid1". Note that if your router asks for a subnetmask, 255.255.255.0 is the equivalent of /24. Setup a second static route for "VPN Tunnel" that also is routed through "Unraid1". On Unraid2: Create a new Tunnel named "Network2-Network1". Switch to Advanced Mode Copy the private and public keys for Unraid2 that you determined above. Take care to use the correct keys or none of this will work. Set the "local tunnel network pool" to the "VPN Tunnel" you chose above Set the "local tunnel address" to the "Unraid2 tunnel IP" from above. Set the "Local endpoint" to the "Endpoint2 DNS" and "Endpoint2 Port" defined above Click Apply Click Add Peer Name it "Unraid1" Choose "LAN to LAN access" Copy the private and public keys for Unraid1 that you determined above Copy the preshared key from above Set the "Peer tunnel address" to the "Unraid1 tunnel IP" defined above Set the "Peer endpoint" to the "Endpoint1 DNS" and "Endpoint1 Port" defined above Set "Peer allowed IPs" to the "VPN Tunnel" and "Network1" defined above, with a comma between. i.e. "10.252.100.0/24, 192.168.1.0/24" Click Apply Start the Tunnel On Router2: If UPnP is disabled, setup a port forward for "Endpoint2 Port" (UDP) that points to "Unraid2" Setup a static route for all of "Network1" that is routed through "Unraid2". Setup a second static route for "VPN Tunnel" that also is routed through "Unraid2". Hopefully at this point your tunnels will connect and devices on one network will be able to reach devices on the other network (by IP address at least, probably not by name) Troubleshooting this will be tough, there is a lot of room for error. I don't have a lot of advice here, just double check that you are using the right values for Unraid1 vs Unraid2 and Network1 vs Network2, etc.

Here's a OneDark theme I made: I've also set the following in Unraid Settings -> Display Settings: If you would like to try it, I've attached a zip file which you can import via Theme Engine. OneDark-black.zip