aliases:
tags:
- Type/Tech
- area/tech
- proto
publish: true
version: 1
dateCreated: 2023-07-14, 14:51
dateModified: 2024-04-21, 13:55
from:
- "[[Homelab & Self-hosting]]"
related:
- "[[RAID]]"
- "[[Data]]"
- "[[Containers|Container]]"
contra:
to:
![]() |
Unraid is a proprietary Linux-based operating system designed to run on home media server setups that operates as a network-attached storage device, application server, and virtualization host. Unraid is proprietary software developed and maintained by Lime Technology, Inc. Users of the software are encouraged to write and use plugins and Docker applications to extend the functionality of their systems. |
---|---|
wikipedia:: Unraid | |
url:: Unraid | |
subreddit:: Unraid: Unleash Your Hardware |
First we're going to create the wg0 config file. (we are using wiregaurd because openvpn is an older standard and has a longer round trip and slower speeds)
Log into your Mullvad account and navigate to this page
Click Linux and Generate a key
Find what server you want. If strictly for downloading I would recommend a lower congestion server. Ie: if in LA pick an AZ server etc. Select "Only IPV4" <--- Container will not run w/ Ipv6 and then download the zip archive
Extract a wireguard file from the archive --They will be named "mullvad-us161.conf". right click and Rename this file to wg0.conf . Make sure it saves as a .conf file and not a .conf.txt file
Go to your binhex vpn container of choice (I'm using binhex-privoxyvpn but this works for any of his containers w/ vpn). And select these settings. Do Not enter a username or password. Custom for the vpn_provider and wiregaurd VPN_CLIENT. Start the container without the file. This will generate your wiregaurd folder.
The container will stop on it's own due to no vpn tunnel connection. Go to your favorite SFTP tool (or SMB share) and navigate to your "/mnt/user/appdata/binhex-YOURVPNCONTAINERNAME/wireguard" and drop the wg0 file in.
Start your container and open the console for the container and enter:
- Stop the array
- Unassign the old drive if still assigned (to unassign, set it to No Device)
- Power down
- [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing)
- Install the new drive
- Power on
- Assign the new drive in the slot of the old drive
- Go to the Main -> Array Operation section
- Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button
- The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives
- : All of the contents of the old drive will be copied onto the new drive, making it an exact replacement, except possibly with more capacity than the old drive.
- Stop the array, unassign the disk, start the array in maintenance mode, stop it again, reassign the drive to the same slot. The idea is to start the array temporarily with the drive “missing” so it changes from “disabled” to “emulated” status, then to stop it and “replace” the drive to get it back to “active” status. - [How do I re-enable a disabled disk drive??? : r/unRAID](https://www.reddit.com/r/unRAID/comments/u3nhmg/how_do_i_reenable_a_disabled_disk_drive/)
cp <your_png_file_path> /boot/config/plugins/dynamix/banner.png
Please keep in mind that when defining connections from an application to another application in the same VPN container network that you will need to set the host to 'localhost' and NOT the LAN IP address, this is because the applications are now bound to the same network and thus should communicate over 'localhost' and NOT the unRAID host IP address.
The order of containers starting is now important, the VPN container must start first in order for the other container(s) to route through it, ordering can be changed in the unRAID Web UI by dragging the containers up and down, the unRAID Web UI shows the start order in descending order.