Open ItsNoted opened 1 year ago
Looks like you might be using cloud flare DNS. Archive.is will not work with cloud flare DNS.
Here's an explanation for the reasons: https://blog.archive.today/post/634795612966125568/when-will-your-site-be-accessible-from-cloudflare
Here's an explanation for the reasons: https://blog.archive.today/post/634795612966125568/when-will-your-site-be-accessible-from-cloudflare
The irony is I cannot even access that blog article.
Here's an explanation for the reasons: https://blog.archive.today/post/634795612966125568/when-will-your-site-be-accessible-from-cloudflare
The irony is I cannot even access that blog article.
Try switching your DNS to the one from your ISP or some other public DNS, e.g. Google public DNS.
I was able to get to it over a VPN. Weird. But that statement was written 3 years ago.
Are you hosting espial on a cloud server? I had gotten this quite a bit when hosting on the cloud. My assumption was that IP range was flagged by whomever to trigger captchas. My solution was to utilize the ARCHIVE_SOCKS_PROXY_HOST/ARCHIVE_SOCKS_PROXY_PORT environment variables to proxy the archive requests to one of my machines I run at home which avoids the captcha.
I will update the docker image; most of the updates previously have just been updates to base libraries, but i'll do another update. I've been a bit busy so haven't really added many features lately, but there are some I'm planning on getting around too based on what's in the github issues
I was able to get to it over a VPN. Weird. But that statement was written 3 years ago.
Well, the concerns are still valid. I'd say even more so, after kiwifarms drop.
I'm curious if this could work with Archive Box so we could self-host our own archives and not sorry about a 3rd party to do the job. Having something off-site is nice but there are caveats like this sometimes.
perhaps, but would have to figure out if it's an "official" integration or make some kind of configuration to support it.. definitely don't want to force users to jump through extra configuration system-setup hoops. maybe it's an additional docker variant.
Given the rise of AI slop and the recent attacks on the Internet Archive, having a local archive feels like it could be a good thing. As a really simple first-step hack could the archive service domain be configurable? Then it should be possible to hack something up that talks the same "protocol" as archive.li ..
It appears for me that when I try to send a page to be archived to archive.is it just gets stuck on the captcha page. I also noticed the Docker image hasn't been updated in over a year. Maybe that is the issue? Any plans to update the image?