[GH-ISSUE #1570] Bug: Extractor archive.org "Failed to find "content-location" URL header in Archive.org response." #938

New issue

Open

opened 2026-03-01 14:47:25 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 14:47:25 +03:00

Owner

Originally created by @robertospenha on GitHub (Oct 27, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1570

Hello developers

I'm using the stable docker image called latest on dockerhub from 6 months ago.

I'm running on an ubuntu 24.04 virtual machine with gnome in a situation where I have almost no additional programs other than the standard ubuntu and I've created other VMs for testing just for that.

In all situations I had the same error even using different sites to save the sites.

Two items always give an error and don't save, which are “git” and “archive.org”. as shown in the image below they are transparent.

What bothered me most was that the downloaded site was not passed on to archive.org.

Another thing that made me realize that it wasn't just me yesterday and today. It was a recent video on youtube in which the channel presents the archivebox project and used docker compose and had the same problem on several sites even though he didn't mention this apparent limitation

Link video: https://www.youtube.com/watch?v=jNeybjyxtMM

Thank you for your attention and I look forward to hearing from you

Originally created by @robertospenha on GitHub (Oct 27, 2024). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1570 Hello developers I'm using the stable docker image called latest on dockerhub from 6 months ago. I'm running on an ubuntu 24.04 virtual machine with gnome in a situation where I have almost no additional programs other than the standard ubuntu and I've created other VMs for testing just for that. In all situations I had the same error even using different sites to save the sites. Two items always give an error and don't save, which are “git” and “archive.org”. as shown in the image below they are transparent. What bothered me most was that the downloaded site was not passed on to archive.org. ![Image](https://github.com/user-attachments/assets/44e93ea2-acd2-47e4-bf95-107d2f6a77bb) ![Image](https://github.com/user-attachments/assets/32d983ab-f479-415c-b87d-adefa01e2b66) Another thing that made me realize that it wasn't just me yesterday and today. It was a recent video on youtube in which the channel presents the archivebox project and used docker compose and had the same problem on several sites even though he didn't mention this apparent limitation ![Image](https://github.com/user-attachments/assets/4ff8bdfc-a568-48b3-a89c-882f7af651be) Link video: https://www.youtube.com/watch?v=jNeybjyxtMM Thank you for your attention and I look forward to hearing from you

kerem commented

2026-03-01 14:47:26 +03:00

Author

Owner

@robertospenha commented on GitHub (Oct 27, 2024):

I think you might have a reason about the archive.org..

It may have been related to the hacker attack they had.

Second post on their blog is temporarily suspended uploading to the site.

https://blog.archive.org/2024/10/21/internet-archive-services-update-2024-10-21/

How I started using the archivebox this week could have been exactly why. And the case mentioned above the channel of youtube may have been because of this also since it is a recent video.

@robertospenha commented on GitHub (Oct 27, 2024): I think you might have a reason about the archive.org.. It may have been related to the hacker attack they had. Second post on their blog is temporarily suspended uploading to the site. https://blog.archive.org/2024/10/21/internet-archive-services-update-2024-10-21/ How I started using the archivebox this week could have been exactly why. And the case mentioned above the channel of youtube may have been because of this also since it is a recent video.

kerem commented

2026-03-01 14:47:26 +03:00

Author

Owner

@pirate commented on GitHub (Oct 27, 2024):

Yeah I was about to post the same, Archive.org has been in read-only mode the last week. It's expected for any new URLs to fail saving because they disabled Save-Page-Now during the attack.

@pirate commented on GitHub (Oct 27, 2024): Yeah I was about to post the same, Archive.org has been in read-only mode the last week. It's expected for any new URLs to fail saving because they disabled Save-Page-Now during the attack.

kerem commented

2026-03-01 14:47:26 +03:00

Author

Owner

@jessienab commented on GitHub (Sep 10, 2025):

So this is still happening, well after the Archive.org attack... surely other add-ons that push to Save Page Now have been working.

Archivebox 0.7.3

@jessienab commented on GitHub (Sep 10, 2025): So this is still happening, well after the Archive.org attack... surely other add-ons that push to Save Page Now have been working. Archivebox 0.7.3