I’m getting overrun with these even when the site is working fine. Sometimes will even have a post load, but as I’m reading it it’ll disappear and I’ll get a bunch of bad gateway popups at the bottom.
At the moment it seems to have cooled off after some minutes ago when it was happening constantly, but since it seemed (to my very untrained eye) to be unrelated to server maintenance I wanted to bring this up.
Edited to add - I had to uninstall and reinstall Connect, but now that has largely fixed the errors. I continually got error messages saying Lemmy.world was down for maintenance when it wasn’t, but since reinstalling it it’s been fine.
bad gateway errors are only caused by server issues. Can’t do much about it as someone using tge site but wait for the server admins to fix the issue.
Yup. There’s not much I can do on Connect’s side, all of the servers are getting hammered with traffic. I added retries to some of the API calls but if the server isn’t responding no amount of retries will help. I’d expect things to settle down eventually.
This is pretty much what I figured. Just losing my mind a bit when it loads fine and then disappears as I’m reading it for seemingly no reason lol.
I’m expecting the growing pains to continue for a while so I’m not that worried.
I’m getting this quite a bit as well. Ironically, I got it on this post as well 😂
deleted by creator
it concerns me as a whole, it’s been happening for 3 weeks now, I’m chalking it down as the backbone just can’t keep up with it, there’s quite a few open issues on the Github(the lemmy one) for optimization and performance errors, I honestly don’t think Lemmy is going to be able to handle the influx of users at a large scale without some of those issues being addressed. I’m going to hold out but, I can forsee people deciding it’s not worth having to wait 40 seconds for a comment to post, or having to refresh multiple times due to Api errors. Hopefully they can get it straightened out
for point of ref; this comment it took 70 seconds to post using connect, and when I tried to go back to home I was met with the 500 error
I was just experiencing this too while using Thunder. I switched over to wefwef and it’s having any easier time fetching posts currently.
That’s just coincidence. Bad gateway errors are cause by server side stability issues or misconfiguration
I’m getting the same thing on Connect
