the instance is going down for a bit at 8 AM GMT on November 12th to finally put us behind iocaine, which should hopefully reduce or eliminate the amount of 503 errors we’re seeing (since all of them are scrapers pushing over the instance) and expose some metrics for admins trying to keep track of how our instance is performing

I’m also working on a bit of a treat for our regulars who’ve been putting up with the 503s for a while. that will probably be announced a bit after the downtime completes.

  • o7___o7@awful.systemsEnglish
    4·
    16 hours ago

    Thanks for all the hard work! Running like a champ for me.

    Just an fyi, www.awful.systems is giving me a 421 error at the moment. Maybe the dns record for the subdomain needs updating (or hasn’t propagated yet)?

    Apologies in advance if i’m being a goober.

    Edit: it works!

    • froztbyte@awful.systemsEnglish
      4·
      1 day ago

      lol I didn’t even know that subdomain existed

      421 is part of the defense check, probably just an unhandled fqdn in the config

      e: records match, so yeah probably just unhandled fqdn. have pinged @self

    • self@awful.systemsOPMEnglish
      4·
      2 days ago

      ah, 421 is what iocaine returns when the request isn’t garbage but there’s no endpoint to handle it, so I might just need to configure an explicit redirect from www.awful.systems to awful.systems in nginx

      • froztbyte@awful.systemsEnglish
        5·
        1 day ago

        a most wonderful stanza:

          server_name ...;
  rewrite  ^ https://$server_name$request_uri? redirect;

        not strictly applicable in this case ofc (it specifically is for https upgrade while keeping all other bits), but I just figured I’d put it here so other people can crib it

        (the amount of god-awful regex matching I’ve seen for that before…)

    • self@awful.systemsOPMEnglish
      3·
      1 day ago

      I think this should be fixed now! for me in both firefox and curl, www.awful.systems now redirects to awful.systems.