It seems to me that about 20% to 50% of when I click on a post here, or reload a page or something, I get an error. Is it only me, or does the server not have enough resources or something?

  • eerongal ( eerongal@ttrpg.network ) 
    link
    fedilink
    arrow-up
    10
    ·
    8 months ago

    Hey there, we swapped to a new host back in December after our old host went out of business. So far the results have been… lackluster. I’ve been reporting to the host when I notice outages, which seem to be reasonably frequent unfortunately.

      • eerongal ( eerongal@ttrpg.network ) 
        link
        fedilink
        arrow-up
        3
        ·
        8 months ago

        Certainly always appreciated. I will continue working with the host; It’s worth noting that things have gotten better than we first migrated. I prepaid for a year with the host because there was a 10% discount vs monthly, so somewhat locked in at the moment (not really locked in, but ya know, sunk costs), so we’ll see where we’re sitting as the year goes on.

          • Enfors ( Enfors@ttrpg.network ) OP
            link
            fedilink
            arrow-up
            1
            ·
            8 months ago

            But I always accessing ttrpg.network. That’s the server I use. So if I “hit a server” which is having issue - this is the one. It doesn’t matter that content is federated in from other servers - I’m not accessing them directly, I’m just going to https://ttrpg.network/.

            • eerongal ( eerongal@ttrpg.network ) 
              link
              fedilink
              arrow-up
              2
              ·
              8 months ago

              federated content lives on its original server for non-text stuff; Posts and comments federate over, but stuff like images are basically proxied to your current instance. If you go into a post that is from another server and there are images, it will go to TTRPG.network to begin to load, then need to load those resources from the remote instance, so there is a bit of a hop/back-and-forth there. There could be lag between instances that could cause issues.