HomeSearchPrevious dayNext day

03:15:46DogsRNice quits [Read error: Connection reset by peer]
05:16:53atphoenix__ (atphoenix) joins
05:19:37atphoenix_ quits [Ping timeout: 268 seconds]
07:02:04grill_ (grill) joins
07:05:19grill quits [Ping timeout: 248 seconds]
08:17:50dendory quits [Ping timeout: 268 seconds]
08:18:36dendory (dendory) joins
08:30:10dendory quits [Ping timeout: 268 seconds]
08:37:46dendory (dendory) joins
08:55:44<tzt>never got this before "You have reached your daily not-logged-in bandwidth limit. Please email us at "info@archive.org" if you would like to discuss this more."
09:09:15pabs quits [Read error: Connection reset by peer]
09:10:29pabs (pabs) joins
10:08:17KoalaBear quits [Read error: Connection reset by peer]
10:09:55KoalaBear joins
10:34:56<@arkiver>tzt: what did you get this one? the wayback machine?
10:37:33<klea>I suppose, or downloading items.
10:37:58<klea>IIRC There's a collection of items that are ARId only to require being logged in due to bandwidth concerns.
14:37:39grill_ is now known as grill
14:46:20unknownsrc quits [Ping timeout: 268 seconds]
15:03:48unknownsrc (unknownsrc) joins
15:23:12Matthww quits [Quit: The Lounge - https://thelounge.chat]
15:26:06Matthww joins
15:35:42<nicolas17>I didn't know WBM even knew whether you were logged in
15:36:08<justauser>This is an SPN error. I think the limit is a few GBs for a logged-in user.
15:36:09<justauser>And yes, it knows. Logged-in users get bigger limits and more features.
15:36:27<nicolas17>ah SPN
16:11:55<klea>2026-06-22 14:54:05 <justauser> Jason says known problem: https://bsky.app/profile/textfiles.com/post/3mott2ynumc2o . <- They are "doing some required maintenance/optimizing of data to make things run smoother on the back end", https://bsky.app/profile/textfiles.com/post/3movy2z4dnc2v
16:33:23MrMcNuggets (MrMcNuggets) joins
16:34:52MrMcNugg1 quits [Ping timeout: 268 seconds]
16:53:05ThreeHM quits [Read error: Connection reset by peer]
16:56:44ThreeHM (ThreeHeadedMonkey) joins
18:11:41<justauser>Got 500 from search.
18:11:53<justauser>Error details: backend_request search: [BACKEND_ERROR] Invalid or no response from Elasticsearch, received: <!doctype html> <html lang=en> <title>500 Internal Server Error</title> <h1>Internal Server Error</h1> <p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error
18:11:53<justauser>in the application.</p> ; Elasticsearch returned undecodable JSON of length 265):
18:11:53<justauser>%3C%21doctype+html%3E%0A%3Chtml+lang%3Den%3E%0A%3Ctitle%3E500+Internal+Server+Error%3C%2Ftitle%3E%0A%3Ch1%3EInternal+Server+Error%3C%2Fh1%3E%0A%3Cp%3EThe+server+encountered+an+internal+error+and+was+unable+to+complete+your+request.+Either+the+server+is+overloaded+or+there+is+an+error+in+the+application.%3C%2Fp%3E%0A
18:26:57<vics>I get 429 Too Many Requests from https://web.archive.org/ . I use a VPS as proxy because of internet censorship in my country. I understand that this VPS IPv4 (or even V6 as it is available) is in some blacklist. I made a quick search on my IPv4 in some blacklist search sites, all OK, all green. Is it possible to find out which exact blacklist(s) web.archive.org use? Or whom can I contact with my IP addresses to resolve the issue?
18:28:03<justauser>Nobody speaks about any details, but I think it's real Too Many Requests - someone in your network poked archive.org itself too hard.
18:28:20<justauser>Try Tor - most of the time it's not blocked.
18:30:14<vics>https://archive.org/ is available though via the same proxy/VPS
18:54:22<IDK>vics: is your vps on AWS?
18:54:32<IDK>in my experience IA doesnt really like AWS traffic
18:55:10<IDK>well, used to at least
18:56:34<vics>IDK: No, on https://contabo.com.
18:57:31<vics>BTW https://www.wikipedia.org returns Error Too many requests. Please email noc@wikimedia.org for more information. (445f43b) as well…
18:59:10DogsRNice joins

HomeSearchPrevious dayNext day