[06:08] I just noticed that http://warriorhq.archiveteam.org/projects.json gives a repository for URLTeam as https://github.com/soult/tinyback.git when really it's https://github.com/ArchiveTeam/tinyback.git [06:08] the soult one is a 404 [06:09] I don't know what's up with that, but it choked up a script I had running, and I wanted to pass the information along to those who could do something about it [08:43] tungol: Thanks man, will update that [22:20] Is this the right place to be asking for "tech support" with the warrior? [22:22] i'm having real trouble getting to my warrior's config page [22:22] localhost:8001 doesn't give me anything [22:23] localhost? not sure that's right if you're running the Warrior VM image - you'll need to substitute the VM's IP address - I think it should show it on the console once it's booted [22:24] ah [22:24] hang on then [22:24] (there are other people here who are vastly more qualified to give advice than I am, to be honest, but I figured I might as well chip in rather than leave you hanging!) [22:25] cool, thanks. do i use a nat or bridged adapter in virtualbox? [22:26] if you know, that is [22:26] i'm just glad o' the help [22:27] depends on your setup. NAT should always work, so go for that if you're not sure [22:27] hmmm. i'm set to that. any easy way for me to find the ip of the warrior's vm? [22:30] I'd have expected it to show it at boot - I think mine says 'connect to http://aaa.bbb.ccc.ddd:8001/ to manage your Warrior' or something - if not, you could try pressing (I think) Ctrl-Alt-F2 to switch to another console where you should be able to login as root with password archiveteam (from memory!) [22:30] then type ifconfig and it should hopefully list the IP address there. [22:30] however - you could try switching to bridged networking and rebooting, that might give you better luck if you're on a typical domestic network [22:32] (not sure why it wouldn't work with NAT, to be honest, but I use VMware rather than VirtualBox so...) [22:32] yeah. when my warrior boots, it says to go to localhost to manage it. but presumably that localhost to the warrior, not the host system running it [22:33] yep, exactly right - hmm [22:34] one moment, let me have a ferret to make sure I'm not talking complete rubbish [22:36] hmm, I'm sorry - the instructions at http://www.archiveteam.org/index.php?title=ArchiveTeam_Warrior use the localhost address too - so this might be a VirtualBox thing that I'm not familiar with. but if it's not working for you... [22:37] did you try the networking option both ways? bridged is probably worth a shot if you're on a typical network, since it should then grab an IP from DHCP I believe [22:38] yeah. looking at the talk on the wiki page (last item), it seems to be a thing [22:38] digging into the terminal i go then :P [22:40] heh, I was just reading exactly that. good luck! [22:41] could've sworn mine gave the IP, but then I did mess around in the config late one night to give it a static address (no DHCP on the network where mine runs - alas I can't get to it from home, either, or I'd have a dig around and see what's what) [22:41] might have to bolt it down to a special ip or get appallingly creative with port mapping (yeesh) [22:44] yes, probably wouldn't hurt - at least you'd know where it is when you want to give it a poke! [22:45] would be nice to be able to fiddle with it from work over my .com [22:58] hmm. so, it appears that if it's in NAT mode, it can't reach github to update :S [23:00] hmm - that's odd - kinda defeats the purpose of having a NAT mode in VirtualBox if it won't let it connect out! perhaps a VirtualBox config issue? [23:01] wouldn't be surprised. i smell a clean install of the home server at some point. ugh. [23:01] (in VMware the NAT mode involves a little private DHCP server and a NAT service, I'd presume VirtualBox would have set something similar up if it offers a NAT option in the config!) [23:05] i'm not trusting virtualbox as far as i can throw it at the moment. [23:06] i'm eyeing up a core 2 duo beige box doing nothing and wondering if there was just an ISO i can burn to install on the bare metal rather than the intermediary vm-iness [23:08] I think the VM is set up to expect certain hard drive configurations - it automatically partitions the secondary drive image, as I understand it - but you should be able to run the scripts under Debian (at least), if that floats your boat [23:09] got an OS on the spare box at the moment? [23:09] hmm. maybe a wet weekend project [23:09] heh. what's the forecast for this weekend like? I think I saw rain... [23:10] xp. totally torchable [23:10] try installing VMware Player - that should accept the OVA/OVF file, I believe [23:11] hmm. might be worth a punt [23:11] I wouldn't suggest it on a machine that wasn't spare, but at least it would eliminate any VirtualBox weirdness [23:11] true [23:11] might have to shoot out and buy a vga cable for the tv [23:22] right, afraid I need to hit the hay - good luck with getting it sorted, quercus - perhaps somebody with more VirtualBox knowledge will pipe up :S [23:22] sorry I couldn't be more useful! [23:23] hey, all help gratefully received