Using a desktop web browser…

It doesn’t seem like a timeout, it is always fast to respond with the error and also fast on successful loading pages. It seems to me there is some kind of resource/parameter starvation in nginx or the nginx bridges to the NodeJS app…

I’m also seeing problems with static content loading, images and css files not loading and getting a mangled half-generated page or missing icons for upvote/downvote that I have to refresh the browser with. This happens at least 1 in 8 refreshes of the page.

  • RoundSparrow@lemmy.mlOP
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I spent the past 20 minutes reading over on Beehaw.org instance, and the same problem is happening there. Pages always load or fail fast, but nginx 500 errors come in batches - where for 20 seconds I instantly get broken page/error page. And then the site resumes normal operation.

    • Slashzero@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      I’ve seen similar behavior (fail fast,) when there are outbound networking issues from any of the service containers. In one instance, lemmy backend was not able to make any outbound connections to any external services. It wild fail in milliseconds and show a timeout error in the logs.

      One hypothesis here could be there are sporadic network issues on the lemmy.ml servers. 🤷‍♂️