sorted by: new top controversial old
Downtime - fedia.social and other instances in c/fediverse@lemmy.world
Downtime - fedia.social and other instances in c/fediverse@lemmy.world
Downtime - fedia.social and other instances in c/fediverse@lemmy.world
[–] 3 points 2 weeks ago (4 children)

I just checked and it was indeed the firewall. The app you use causes a lot of 404’s which crowdsec interprets as crawling and so blocked your IP. I unblocked and working on fixing crowdsec so it stops happening.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Downtime - fedia.social and other instances in c/fediverse@lemmy.world
    infosec.pub down (update: back online; was due to anti-bot experiments) in c/isitdown@infosec.pub
    [–] 5 points 2 weeks ago (1 child)

    I implemented some perhaps overly ambitious firewalling in an attempt to keep the ai scrapers at bay, so I suspect it does appear to be down. And I clearly have to find and fix whatever is causing that.

  • permalink
  • fedilink
  • source
  • parent
  • context
    • infosec.pub down (update: back online; was due to anti-bot experiments) in c/isitdown@infosec.pub
    Anonymous access to infosec.pub is disabled temporarily in c/infosecpub@infosec.pub
    [–] [S] 1 point 2 months ago (1 child)

    I think it is because I disabled anonymous access due to the AI scrapers continuously causing the instance to crash. I just reenabled anonymous access which should allow it to be indexed by those sites, but it may cause some instability

  • permalink
  • fedilink
  • source
  • parent
  • context
    • Hetzner prices have skyrocketed (up to 3x); how will this affect your Fediverse server? in c/fediverse@lemmy.world
    [–] 31 points 4 months ago (1 child)

    There was a big price increase a month or two ago that affected existing servers. I think this is recognizing that Hetzner just can’t acquire new servers (particularly memory) at anywhere close to what they could before. RAM prices are up about 400% in the past year and rising, and I think even server chassis and CPUs are being largely soaked up by the mesoscale datacenter builds.

    Net net, this sucks. And my expectation is that Hetzner will still be the cheapest game in town by about the same percentages as before. It the costs keep going up, I think we will see the fediverse starting to struggle.

    Between the absolute crush of bot registrations and the spiraling costs, I have been contemplating moving to a required donation for new accounts.

  • permalink
  • fedilink
  • source
    •
    Congress Just Snuck In Uber Immunity in c/politics@lemmy.world
    Lack of content - are we not federated? in c/infosecpub@infosec.pub
    Lack of content - are we not federated? in c/infosecpub@infosec.pub
    20
    Federation issue and image issue should be fixed now. (infosec.pub)
     

    Federation broke after I upgraded to lemmy 0.19.19 (I tend to apply security updates relatively fast). Unfortunately, that broke federation due to some issues in the release. The issue is described here: https://github.com/LemmyNet/lemmy/issues/6581 - they've not released a fixed version yet, but that was easy enough to sort out manually.

    There was also an image issue. I don't know what happened there, but imagemagick was consistently failing - once I restarted the containers, that problem seems to have gone away. I don't know if it will return or was something held over from the update - perhaps an unclean restart. I'll keep an eye on it, but let me know if you see it again.

    Infosec.pub destroys image quality in c/infosecpub@infosec.pub
    1
    infosec.pub downtime - December 14 (infosec.pub)
     

    The following instances will be offline briefly on Saturday, December 14 from 9am ET / 2pm UTC for approxmately 10 minutes: infosec.exchange infosec.town infosec.pub pixel.infosec.exchange books.infosec.exchange matrix/element.infosec.exchange relay.infosec.exchange meetup.infosec.exchange video.infosec.exchange infosec.press infosec.place fedia.io fedia.social elk,.infosec.exchange infosec.space convo.casa

    The servers supporting these instances require a reboot. The Dell servers these instances run on take a very long time to boot, so I am estimating 10 minutes of downtime. It could be more, could be less.

    We use live patches to minimize reboots needed for patching, however Ubuntu only provides livepatch support for a year, which is how long most of these systems have been running for.

    view more: next ›