@themusicman@lemmy.world to Programmer Humor@lemmy.ml • 1 year agoLemmylemmy.worldimagemessage-square76fedilinkarrow-up1385cross-posted to: 196@lemmy.blahaj.zone
arrow-up1385imageLemmylemmy.world@themusicman@lemmy.world to Programmer Humor@lemmy.ml • 1 year agomessage-square76fedilinkcross-posted to: 196@lemmy.blahaj.zone
minus-squareggnoredolinkfedilink23•1 year agothat’s Jerboa issue but probably because It received something from the server that it shouldn’t
minus-squareAtemulinkfedilink18•1 year agoNo, the server gave a 502 instead of a JSON and Jerboa doesn’t handle that gracefully.
minus-squareTheGenerallinkfedilink0•1 year agoSeems like the 4 apps I use all have the same issue though which makes me wonder if it’s something in Lemmy causing the issue (not the apps).
minus-squareAtemulinkfedilink9•edit-21 year agoWell, Lemmy shouldn’t 502 in the first place. That’s the root cause. The apps should handle that gracefully though, especially given how commonly Lemmy throws a 502.
minus-square@Distributed@lemmy.mllinkfedilink1•1 year agoIts an nginx issue, unable to reach the server because it’s over capacity. Seems to be mostly because of sql
that’s Jerboa issue but probably because It received something from the server that it shouldn’t
No, the server gave a 502 instead of a JSON and Jerboa doesn’t handle that gracefully.
Actually i was trying to say similar issue
Seems like the 4 apps I use all have the same issue though which makes me wonder if it’s something in Lemmy causing the issue (not the apps).
Well, Lemmy shouldn’t 502 in the first place. That’s the root cause. The apps should handle that gracefully though, especially given how commonly Lemmy throws a 502.
deleted by creator
Its an nginx issue, unable to reach the server because it’s over capacity. Seems to be mostly because of sql