Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

https://archive.is/7ytlz

I think we hugged it to death.



It's kind of sad that sweden.se can't handle a couple of thousand visitors under a short period of time.


sweden.se is fine; it's identity.sweden.se that's having some problems. This is a really limited site with a target audience that's normally in the hundreds, perhaps thousands, of developers. It's probably just running on a cheap server/VPS somewhere, which is fine almost all of the time.


No, it's running on debroome which uses AWS.


It is, my Pi 2 could handle 10,000 req/s and this page could easily be cached or even static. What kind of traffic does the HN frontpage generate?


Sorry, I know HN isn’t a support forum, but am I the only one who gets “Safari couldn’t establish a secure connection” to any of the archive.xx sites? It’s been happening for ages now.


Are you using Cloudflare's 1.1.1.1 DNS by any chance?


No, I use Apple's Private Relay which might route via Cloudflare but I've tried it with it turned off and it makes no difference.

It must be something in my network path because I just tethered to my phone's 4G connection and it works. Odd.


Does Cloudflare DNS block it? Or are you proposing Cloudflare DNS as a solution?


It's a long story! https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

In short if you use Cloudflare's 1.1.1.1 DNS then some archive.is domains won't load so you should perhaps use another DNS server.

Edit: Not because 1.1.1.1 is in the wrong it is just what the person behind archive.is recommends as he will not be changing his position and neither will Cloudflare so it's a bit of a stalemate.


Interesting. If this becomes a widespread practice, I suppose Cloudflare could start including bogus client subnet values in its upstream requests.


this story does more to persuade me to switch to 1.1.1.1


It's the other way around. The site blocks Cloudflare for some political reasons that have been mentioned here before, but I can't remember what they were.


I thought it was because Cloudflare DNS doesn't pass on the full IP subnet of the requesting computer, which archive.is wants. archive.is says they need it for better CDN routing, CloudFlare says it's a privacy violation and there are enough CloudFlare PoPs to provide for CDN granularity just by going off the requesting server.


I’ve been experiencing this intermittently lately as well.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: