▲ 9 ▼ What is up with the frequent little outages with ttrpg.network? (ttrpg.network) submitted 5 months ago by Enfors@ttrpg.network to c/community_meta@ttrpg.network 10 comments fedilink hide all child comments 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?
[–] rosswinn@ttrpg.network 1 point 5 months ago (1 child) you might have hit a server that was having an issue. permalink fedilink source parent hideshow 2 child comments replies: [–] Enfors@ttrpg.network [S] 1 point 5 months ago* (1 child) 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/. permalink fedilink source parent hideshow 2 child comments replies: [–] eerongal@ttrpg.network 2 points 5 months ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Enfors@ttrpg.network [S] 1 point 5 months ago Right, but that shouldn't give me a 404, bad gateway, or gateway timeout from ttrpg.network itself - which is what tends to happen. permalink fedilink source parent
[–] Enfors@ttrpg.network [S] 1 point 5 months ago* (1 child) 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/. permalink fedilink source parent hideshow 2 child comments replies: [–] eerongal@ttrpg.network 2 points 5 months ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Enfors@ttrpg.network [S] 1 point 5 months ago Right, but that shouldn't give me a 404, bad gateway, or gateway timeout from ttrpg.network itself - which is what tends to happen. permalink fedilink source parent
[–] eerongal@ttrpg.network 2 points 5 months ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Enfors@ttrpg.network [S] 1 point 5 months ago Right, but that shouldn't give me a 404, bad gateway, or gateway timeout from ttrpg.network itself - which is what tends to happen. permalink fedilink source parent
[–] Enfors@ttrpg.network [S] 1 point 5 months ago Right, but that shouldn't give me a 404, bad gateway, or gateway timeout from ttrpg.network itself - which is what tends to happen. permalink fedilink source parent