I’m trying to fix this annoying slowness when posting to larger communities. (Just try replying here…) I’ll be doing some restarts of the docker stack and nginx.

Sorry for the inconvenience.

Edit: Well I’ve changed the nginx from running in a docker container to running on the host, but that hasn’t solved the posting slowness…

  • 00Lemming@lemmy.worldEnglish
    16·
    1 year ago

    Godspeed to you over the coming days man. Really appreciate you putting this together and the extra work it takes when tackling something like this (both being new to the platform and the tech still being in relative infancy) - not to mention the crazy scaling happening. I will definitely be pitching in to help make sure the server stays up!!

  • slimerancher@lemmy.worldEnglish
    8·
    1 year ago

    Something is weird.

    I opened this post from main page “subscribed listing”, but the title showed “I can’t find any cannabis cultivation community”, but the comments were same. I initially thought I have opened a wrong post, but the comments were mentioning “Good work Ruud”, so I refreshed and it fixed post’s title.

    Have you noticed the issue?

    • TRBoom@lemmy.worldEnglish
      10·
      1 year ago

      I’ve noticed a couple oddities as well.

      • I refresh a page and a completely different page loads instead
      • An autorefresh hits the community tab, but it loads up 10 posts from a single community I’m sure it’ll get sorted out eventually lol
    • TeaHands@lemmy.worldEnglish
      5·
      1 year ago

      It’s happened to me a few times as well (not just on this instance, think it’s a bug in Lemmy itself). So far I’e not found a reproducible pattern though so it’s a tricky one to bug report effectively.

        • csos95@lemmy.worldEnglish
          5·
          1 year ago

          I had something similar happen yesterday.

          I opened a thread about pokemon, browsed it for a bit, did some stuff in other tabs, and clicked back to the pokemon tab maybe an hour later to browse some more.

          The post had changed to one where a user was asking for relaxing game recommendations and it was loading in new comments that seemed to be from that post, but I could still see the comments that had already loaded from the pokemon post when I scrolled down.

          When I refreshed it changed back to the pokemon post and only showed comments from that.

  • mo_ztt ✅@lemmy.worldEnglish
    7·
    1 year ago

    Hey, I just want to echo what everyone else is saying - thanks much for hosting + all the efforts to keep things working well. It’s appreciated 👍

    • Ruud@lemmy.worldOPMEnglish
      4·
      1 year ago

      Hmm. I guess the delay in posting is not related to nginx. I now have the same conf as a server that doesn’t have this issue.

      • Acetamide@lemmy.worldEnglish
        21·
        1 year ago

        I’m only familiar with the high-level Lemmy architecture, but could it be related to database indices being rebuilt?

      • azura@fedia.io
        9·
        1 year ago

        You got this. <3
        I don’t have experience scaling Lemmy, but I do have experience scaling stuff in general. I’m sure you’ve got a few people here who’d be willing to talk things through with you if you get too frustrated.
        And don’t forget to breathe and step back if you have to. Your well being is more important.

    • God@lemmy.worldEnglish
      1·
      1 year ago

      Someone said this about Caddy “it injects advertising headers into your responses”. Is this true? I don’t know anything about caddy but that doesn’t sound too good lo (to be fair it could be misinformation).

        • God@lemmy.worldEnglish
          1·
          1 year ago

          Sounds very cool. Does running with that file also handle the SSL certificate and validation automatically? Or are there extra steps?

          • Perhyte@lemmy.worldEnglish
            1·
            1 year ago

            A minimal config like that will default to provisioning (and periodically renewing) an SSL certificate from Let’s Encrypt automatically, and if there are any issues doing so it will try another free CA.

            This requires port 80 and/or 443 to be reachable from the general Internet of course, as that’s where those CAs are.

            There’s an optional extra step of putting

            {
    email admin@emailprovider.com
}

            (with your actual e-mail address substituted) at the top of the config file, so that the Let’s Encrypt knows who you are and can notify you if there are any problems with your certificates. For example, if any of your certificates are about to expire without being renewed1, or if they have to revoke certificates due to a bug on their side2 .

            As long as you don’t need wildcard certificates3, it’s really that easy.

            1: I’ve only had this happen twice: once when I had removed a subdomain from the config (so Caddy did not need to renew), and once when Caddy had “renewed” using the other CA due to network issues while contacting Let’s Encrypt.

            2: Caddy has code to automatically detect revoked certificates and renew or replace them before it becomes an issue, so you can likely ignore this kind of e-mail.

            3: Wildcard certificates are supported, but require an extra line of configuration and adding in a module to support your DNS provider.

  • animist@lemmy.oneEnglish
    5·
    1 year ago

    Since I have you here, if I start my own instance do I absolutely have to use docker? I’ve never had good experiences with it and would rather just install programs the old-fashioned way