• SirLotsaLocksOP
      4·
      4 years ago

      They’re working on it, seems like its rate limited or something like that, if you refresh a couple times you might get in.

        • moksha256
          1·
          4 years ago

          Yeah sorry guys, I was blindsided by the default Lemmy rate limits and was NOT expecting front-age HN so…it was down for like an hour :(

          Should be good now though.

          • nutomicA
            1·
            4 years ago

            Are you passing X-Real-IP and X-Forwarded-For headers to the backend? We had a problem with rate limits due to that recently, the backend was counting all the requests towards the internal IP of lemmy-ui. We fixed it in our repo, but you might be missing that.

            Edit: here’s the code

            • moksha256
              2·
              4 years ago

              Thanks, looks like I’ve got that.

              FWIW, in my case, increasing the value for message in the rate_limit section of lemmy.hjson as well as removing the limit_req_zone parameter in the nginx config did the trick for yesterday’s traffic burst. I’ll probably put them back (or at least reduce them to saner values) once the spike dies down a bit.