_    __      _     ___   __     __ 
| |  / /___  (_)___/ / | / /__  / /_
| | / / __ \/ / __  /  |/ / _ \/ __/
| |/ / /_/ / / /_/ / /|  /  __/ /_  
|___/\____/_/\__,_/_/ |_/\___/\__/  

π’©π‘’π“‰π“Œπ‘œπ“‡π“€π’Ύπ“ƒπ‘” 𝒾𝓃 𝓉𝒽𝑒 𝒢𝑒𝓉𝒽𝑒𝓇. 🌌
--------------------------------β•–
    Running ArchiveTeam Warrior |
    On Proxmox                  |        
--------------------------------|
    Kevin Froman                |
    VoidNetwork LLC             | 
    November 16, 2021           |
    kev[-@-]voidnet.tech	|
--------------------------------╝

	ArchiveTeam[1] is a rag tag team of volunteers dedicated to archiving the web.
Most people reading this blog should be familiar with how things on the web can
go offline (examples: Vine, Geocities, Google Plus). ArchiveTeam helps to ensure
that data remains available. They work proactively even if a service has not been
announced to be shutting down, for example they archive Reddit because of the risk
of increased censorship or shutdown.

	ArchiveTeam Warrior[2] is an appliance by ArchiveTeam that anyone can run
to contribute their bandwidth in archiving the web. This is important because it
distributes the cost, but also because some websites block IPs from downloading too
much or from downloading from non-residential IPs.

	Warrior is advertised for VirtualBox, VMWare, and Docker. Personally, I have
not had a lot of luck running it in Docker, so I prefer to run it in VMs (which is
also somewhat more secure than Docker). I wanted to run it on my home server 24/7,
which I use Proxmox[2] on. Proxmox runs KVM for VMs, so generally anything that can
run in KVM can run in Proxmox. To install the ArchiveTeam warrior appliance, follow
the steps below (This assumes basic install and competence with Proxmox):


0. Create a standard VM. If done from the GUI you have to include a disk, so just set the minimal size and then detach and delete it.
   - Only 1 or 2 cores, and only a gig of ram (maybe less even)
1. Wget the ova from ArchiveTeam's links to your host system
2. Extract it using tar (you may need to rename it to .tar.gz or .tar)
   - you should have a resulting .vmdk file
3. Import the disk
   - On the same host system run: qm importdisk NUMBER_ID_OF_YOUR_VM archiveteam-warrior-xyz.vmdk local-lvm -format qcow2
4. Enable the disk in the hardware settings of your VM. I had to use IDE for the disk.
5. Make sure the VM BIOS will use the disk in the boot order
6. Make sure you have a restrictive firewall set on the VM.
   - To be safest restrict all incoming traffic, including the management interface except when it is needed.
   - Prevent outgoing traffic from reaching private ranges
   - The Warrior is often not particularly up to date, so it can have vulnerable packages.
7. Set start on boot if you want it.
8. When you start the VM, the warrior will auto setup and launch, it will run on port 8001 at time of writing.


(Please note: do not use Tor or VPNs, etc for your Warrior. It can cause issues. There is also a chance of your home IP getting banned.)

------------------------------------------------
1. https://wiki.archiveteam.org/
2. https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior