The network Burggit is on is experiencing performance issues. I’d encourage everyone to use shota.nu for right now if you can. I talked to the host about this and evidently it’s an upstream issue with the datacenter.
The datacenter is refusing to help out with this and thinks everything is working fine so there’s plans for migrating to a new datacenter that are underway sometime soon. So in the meantime, I’m afraid we need to just grin and bear it.
Lemmy errors out if the NFS mount is nonresponsive. It doesn’t like not being able to access the huge swathe of pictures that are stored on the server. I’ve switched the NFS mount to TCP and have it retry the connection every second in an effort to mitigate the severe packet loss.
As I was composing this, the packet loss shot up to 90% so I don’t think even that will help…
That’s really all I can do for right now. I wish there was more that I could do to resolve this… 😔
Which community was it? I’m curious to see what data the server tries to return, assuming I can reproduce this on my end.
E: I noticed that it’s running 0.19.0. Maybe try another server we’re fed’d with that runs an older version to see if this same behavior happens.
!mapmemes@rqd2.net
It outright crashes. The logs don’t show the instance trying to send anything when it happens, so it’s purely a client-sided issue… Do try another community from an instance that’s fed’d that runs an older version of Lemmy to see if it happens with that one too (If you can find one.)
I’m subscribed to other communities on the same server so it was weird that subbing to that one specific community crashes the app.
This appears to be an app issue, then. I scrolled through my subscribed feed on the Boost app and even found a post from that community, and no crashes occurred there. Nothing I can do about it, I’m afraid. I guess report the issue to the maintainer and hope that you don’t get banned for the contents of the report (lol)?