4 ms·

https://archive.is/7ytlz https://archive.is/7ytlz I think we hugged it to death.

• cinntaile 3y ago
  It's kind of sad that sweden.se can't handle a couple of thousand visitors under a short period of time.
  • worksonmine 3y ago
    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?
  • arp242 3y ago
    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.
    • KomoD 3y ago
      No, it's running on debroome which uses AWS.
• jen729w 3y ago
  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.
  • deleted 3y ago
    [deleted]
  • satysin 3y ago
    Are you using Cloudflare's 1.1.1.1 DNS by any chance?
    • arjvik 3y ago
      Does Cloudflare DNS block it? Or are you proposing Cloudflare DNS as a solution?
      • satysin 3y ago
        It's a long story! https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ 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.
        • whatgoodisaroad 3y ago
          this story does more to persuade me to switch to 1.1.1.1
        • arjvik 3y ago
          Interesting. If this becomes a widespread practice, I suppose Cloudflare could start including bogus client subnet values in its upstream requests.
      • hostcontroller 3y ago
        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.
        • kalleboo 3y ago
          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.
  • hultner 3y ago
    I’ve been experiencing this intermittently lately as well.