<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center> <hr><center>nginx/1.18.0 (Ubuntu)</center>
</body> </html>
A 502 Bad Gateway Error is a general indicator that there’s something wrong with a website’s server communication. Which for your case is http://lemmy.world. Basically the instance is struggling so you’re getting these errors. Liftoff can’t do anything about it other than showing you a more friendly error (it should).
Same from Connect (at least with lemmy.world - switching to an account on a less-busy instance and the error goes away)
consider migrating to a smaller instance, lemmy.world is having it pretty rough lately
Unfortunately, lemmy.world has been pretty flaky the last few days, not handling the amount of traffic very well.
Yes. First, having trouble with an update. Now having much more severe trouble with… I’m assuming traffic from Reddit’s death. More frustrating than necessary because there’s been no communication in a few days. Hope they’re just busy figuring it out.
Me too, but until they do it just makes this Lemmy instance - and Lemmy in general - look bad. I do hope they succeed, but I’m not sure the owners of Lemmy instances understand what’s at stake, or what it takes to run a production level service.
Me too, but until they do it just makes this Lemmy instance - and Lemmy in general - look bad. I do hope they succeed, but I’m not sure the owners of Lemmy instances understand what’s at stake, or what it takes to run a production level service.
