Nick Sweeting
Nick Sweeting
if you're running in docker you shouldnt need to mess with or install those 3 manually, but outside of docker to fix it you should just need to run `archivebox...
Please screenshot your extension configuration. I suspect you did not enter the archivebox host correctly / at all as it's empty according to the outputed error above.
Can you screenshot the screen where you click delete
We recently pushed a fix for this. Please upgrade to the `dev` branch pre-release version and see if it's still happening https://github.com/ArchiveBox/ArchiveBox#install-and-run-a-specific-github-branch
What browser?
The archive task actually continues just fine even if the user navigates away after the 504, so I haven't prioritized fixing this but I've been aware of it for a...
Thanks for this PR and the documentation PR to go with it! It looks like it's on a good track so far. Quick question: Where is `REVERSE_PROXY_USER_HEADER` actually handled? I...
This is still alive but very slow moving. If you need an immediate solution I recommend building a quick and dirty GUI to modify the scheduler cron config directly or...
This is somewhat expected, Ubuntu's strict version pinning for apt packages makes it so the default npm install is too old to run the newest single-file version. You have to...
email: `` (use [this page](https://github.com/ArchiveBox/ArchiveBox/security) instead now) or twitter DM `@ArchiveBoxApp`