| 00:00:47 | | qwertyasdfuiopghjkl quits [Ping timeout: 272 seconds] |
| 01:15:22 | | nepeat quits [Ping timeout: 255 seconds] |
| 01:22:49 | | nepeat (nepeat) joins |
| 01:53:57 | | archivist99 joins |
| 02:14:22 | | GNU_world joins |
| 02:15:13 | | archivist99 quits [Ping timeout: 255 seconds] |
| 03:43:31 | | BearFortress_ quits [Client Quit] |
| 03:57:09 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 04:20:34 | | DogsRNice_ quits [Read error: Connection reset by peer] |
| 04:22:39 | | BearFortress joins |
| 07:02:35 | | qwertyasdfuiopghjkl quits [Ping timeout: 272 seconds] |
| 07:03:56 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 07:06:28 | | Unholy236192464537713 (Unholy2361) joins |
| 09:00:01 | | Bleo1826007227196 quits [Client Quit] |
| 09:01:25 | | Bleo1826007227196 joins |
| 10:56:01 | | MrMcNuggets (MrMcNuggets) joins |
| 11:00:02 | | Bleo1826007227196 quits [Client Quit] |
| 11:01:20 | | Bleo1826007227196 joins |
| 11:27:19 | | that_lurker quits [Ping timeout: 272 seconds] |
| 11:40:45 | | that_lurker (that_lurker) joins |
| 13:25:25 | | MrMcNuggets quits [Client Quit] |
| 16:08:12 | | petesimonnn joins |
| 16:12:32 | <petesimonnn> | hello. i am new here and I am in USA. so i got the warrior docker running on a linux cloud server and in the web interface i got the message "Phooey… No warrior projects are available for participation yet!" - is that right? |
| 18:08:00 | | DogsRNice joins |
| 18:16:45 | <TheTechRobo> | petesimonnn: Sounds like your Warrior can't access the Internet. Try restarting it |
| 18:16:45 | <TheTechRobo> | (Hadn't seen that you'd already posted here lol) |
| 18:18:15 | <petesimonnn> | hello thetechrobo. okay i'll try that. first i'll do a ping6 ipv6.google.com from my cloud/hosted server |
| 18:23:30 | <petesimonnn> | ping6 works from the cloud server to the external address. and i ran docker restart <docker-id> that matches the ''archiveteam-warrior" container. the results are the same - No warrior projects are available for participation yet |
| 18:24:05 | <petesimonnn> | oh i should mention that the cloud server use ipv6 only, and not ipv4 |
| 18:25:18 | <TheTechRobo> | IPv6 only could be a problem |
| 18:25:45 | <petesimonnn> | aaah poop. i paid $ for that cloud server haha |
| 18:26:06 | <ilnrja> | you dont get nat ipv4 at all? |
| 18:26:43 | <ilnrja> | maybe it's nat64 |
| 18:26:55 | <ilnrja> | warrior has its own dns settings so it wouldn't work |
| 18:27:10 | <TheTechRobo> | ilnrja: Some server providers give discounts if they don't have to assign you an IPv4 address |
| 18:27:13 | <petesimonnn> | ilnrja - good question. i don't know. i'll send a trouble ticket to the support about this. thanks for the info too 🤓 |
| 18:27:15 | <TheTechRobo> | I assume this is one of those |
| 18:27:56 | <petesimonnn> | thetechrobo - maybe. it was $5 USD for all 6 months |
| 18:28:16 | <TheTechRobo> | wow. What provider is this, out of curiosity? |
| 18:28:29 | <petesimonnn> | i want a refund so i can have a beer for my disappointment hehe 😉 |
| 18:28:46 | <TheTechRobo> | Cc arkiver / JAA - can the tracker be made to support ipv6 feasibly? |
| 18:29:12 | <petesimonnn> | c-servers.co.uk |
| 18:31:41 | <petesimonnn> | i like to search for cloud servers on serverhunter dot com and lowendtalk sites |
| 18:32:42 | <TheTechRobo> | wow, that is cheap indeed |
| 18:33:33 | <petesimonnn> | ilnrja maybe it's nat64. warrior has its own dns settings so it wouldn't work - i suppose i would have to customize the docker container data but i have never done that before |
| 18:34:12 | <petesimonnn> | thetechrobo - yeah it is and as grandpa says, i got what i paid for haha |
| 18:34:36 | <TheTechRobo> | I would get one of those... if my Internet supported IPv6 lol |
| 18:35:20 | <TheTechRobo> | hmm, it says NAT64 is supported on some of them, but it seems they are all out of stock |
| 18:35:35 | <petesimonnn> | yeah odd how ISP pick n choose if ipv6 is supported. it is on Hughesnet satellite service that i have |
| 18:35:44 | <TheTechRobo> | Scratch that, it is supported in all of them |
| 18:35:57 | <petesimonnn> | nat64 is supported on what? and what's out of stock? |
| 18:36:30 | <TheTechRobo> | NAT64 is supported on all of their VPSes it seems |
| 18:36:45 | <TheTechRobo> | Some of the VPSes offer a real (shared) IPv4 but they are out of stock |
| 18:36:46 | <petesimonnn> | and could anyone please give me pointers as to how to customize network config inside the warrior docker file? |
| 18:36:50 | <TheTechRobo> | But you might be able to get NAT64 working |
| 18:37:18 | <petesimonnn> | oh you're talking about the c-servers.co.uk stuff |
| 18:37:21 | <TheTechRobo> | petesimonnn: I would advise not trying to do that yourself, you could cause issues with the archived data |
| 18:37:23 | <TheTechRobo> | petesimonnn: Yeah |
| 18:38:35 | <petesimonnn> | ah double poop. okay |
| 18:41:24 | <petesimonnn> | well, is there another docker image that helps the archiveteam that i could load on my clout server just to try it |
| 18:42:37 | <petesimonnn> | i mean now i'm using the standard warrior docker file from https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior |
| 18:44:12 | <that_lurker> | It seems the project website (warriorhq.archiveteam.org) does not have an AAAA record, so yes the ipv6 only could be an issue |
| 18:46:20 | <petesimonnn> | that_lurker - i am not sure what means, but i can ping6 the address warriorhq.archiveteam.org and an ipv6 address results |
| 18:48:45 | <petesimonnn> | is the standard warrior docker container able to access these address via ipv6? |
| 18:48:46 | <petesimonnn> | Name: warriorhq.archiveteam.org |
| 18:48:46 | <petesimonnn> | Address: 2a01:4f8:c2c:123f:64:5:67e6:8d9c |
| 18:48:47 | <petesimonnn> | Address: 2a00:1098:2b::1:67e6:8d9c |
| 18:48:47 | <petesimonnn> | Address: 2a00:1098:2c::5:67e6:8d9c |
| 18:49:55 | <that_lurker> | have you setup docker to work with ipv6? https://docs.docker.com/config/daemon/ipv6/ |
| 18:51:27 | <petesimonnn> | lurker - hmm i don't know. i guess i should check it. i am using debian 12 on a cloud server and installed docker.io - apt install docker.io - and that's all |
| 18:53:59 | <petesimonnn> | and i am remotely accessing the webui to the warrior in docker from home - http://[2a01:4f9:6b:f831::1]:8001/ |
| 18:57:43 | <petesimonnn> | so i found the wiki page - https://wiki.archiveteam.org/index.php/Running_Archive_Team_Projects_with_Docker#Enabling_IPv6 - and i'll have to tinker with docker. thanks lurker |
| 21:46:16 | <@JAA> | TheTechRobo (Cc arkiver): The tracker (or rather, the API, i.e. the relevant part for worker communication) already supports IPv6, but the warriorhq doesn't, so the warrior can't find the projects etc. Not sure what'd be needed there. However, I don't think it'd help; the warrior also needs to clone the project code repo from GitHub, which still doesn't support IPv6. |
| 21:46:39 | <@JAA> | So working IPv4 is necessary anyway. |
| 22:46:39 | <TheTechRobo> | petesimonnn: Let us know if that works! |
| 22:48:08 | <TheTechRobo> | If you can't get ipv4 to work, running specific projects rather than the entire Warrior might (assuming atdr supports ipv6). |
| 22:48:54 | <@JAA> | Hmm, right, atdr is also IPv4-only currently. |
| 23:24:43 | <petesimonnn> | thetechrobo - okay. JAA - what is atdr ? |
| 23:43:06 | <ilnrja> | nat64 needs to use the isp's dns servers to work, the warrior docker container uses quad9 dns |
| 23:47:17 | <ilnrja> | actually it depends on project, urlteam forces quad9 |