Archive.ph Issues

[Snekposter]

Not sure where else to put this since its not an issue with the forum itself, but I've been getting persistent, ongoing issues connecting to archive.ph/archive.is for a while now, and naturally that makes it hard to read a lot of the articles on this site.

Sometimes that is the error I get when I try to access the sites, other times its the generic "Connection Timed Out" error. Any idea what's going on? I've tried swapping DNS servers already and that hasn't helped.

 

[Hulkster]

Haven't you heard? archive.ph banned users with anime profile pictures after the 8chan shutdown. Get with the times, old man.

 

[c.a9]

This is normal archive.today is a beloved old tool, it shits itself and dies randomly from time to time but I can usually just shake around or fidget with it a little until it works again. No I have no productive answer. Have you tried simply using .md/.fo or something instead.

 

[The Mass Shooter Ron Soye]

Any idea what's going on? I've tried swapping DNS servers already and that hasn't helped.

Use this thread: https://kiwifarms.st/threads/archival-tools.6561/

To solve the nginx error, try clicking "View site information" and clearing cookies and site data for Archive.ph. Then try again.

Or turn off your VPN, or switch to a different VPN IP in a different, clean browser.

One of these will almost certainly work.

 

[Snekposter]

This is normal archive.today is a beloved old tool, it shits itself and dies randomly from time to time but I can usually just shake around or fidget with it a little until it works again. No I have no productive answer. Have you tried simply using .md/.fo or something instead.

Yes, I have, and they all shit themselves. But that does me no good anyways if I can't load the specific site that's been linked in a thread.

Use this thread: https://kiwifarms.st/threads/archival-tools.6561/

To solve the nginx error, try clicking "View site information" and clearing cookies and site data for Archive.ph. Then try again.

Or turn off your VPN, or switch to a different VPN IP in a different, clean browser.

One of these will almost certainly work.

Thanks for the help, but I wound up needing to fuck around with some of my DNS settings instead to fix that. Apparently I had screwed something up somewhere there by accident and it works fine now after doing an ipflush in PowerShell.