Connect for Lemmy App

2790 readers

12 users here now

A community for the mobile app Connect for Lemmy.

Links

founded 2 years ago

MODERATORS

kuro_neko

Bad Gateway errors (lemmy.world)

submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/lemmyconnect

12 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (1 children)

I dunno... I'm having a hard time doing anything on the app, or the website.

The servers are basically on fire.

I do worry if the admins can keep up with additional server capacity. Or if the plan is just to wait for things to revert to the ghost town it was a few weeks ago...

Lemmy.world was, for awhile, rebooting their server on a timer every 15 minutes to un-break it. I'm not sure if that stopped after they upgraded the software over the weekend.

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

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