lemmy.ml meta

1406 readers

1 users here now

Anything about the lemmy.ml instance and its moderation.

For discussion about the Lemmy software project, go to [email protected].

founded 3 years ago

MODERATORS

[email protected]

440

lemmy.ml is migrated to a new server (lemmy.ml)

submitted 1 year ago by [email protected] to c/[email protected]

145 comments fedilink hide all child comments

Its now running on a dedicated server with 6 cores/12 threads and 32 gb ram. I hope this will be enough for the near future. Nevertheless, new users should still prefer to signup on other instances.

This server is financed from donations to the Lemmy project. If you want to support it, please consider donating.

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

[–] [email protected] 9 points 1 year ago (11 children)

@nutomic @liaizon 502 Bad Gateway ?

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (6 children)

I was getting 502 Bad Gateway. When I pinged Lemmy.ml I got an IPV6 address. It disabled IPV6 on my local computer and now when I ping I get a IPV4 IP address it works now.

I am wondering if DNS is screwed up on the IPV6 network for Lemmy.ml.

~~Note. This could totally be something on my end, I really haven't done much with IPV6 but it did solve the 502 Error so I might do the same for you. ~~

Edit. Multiple people are reporting the same thing I am seeing. It is defiantly something about IPV6 on the lemmy.ml server end.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

Thanks for mentioning the IPv6, I've been banging my head all day trying to figure out why I kept getting the 502 yet no one was complaining anywhere and isitdown was showing the server as Up.

I forces my DNS to resolve only IPv4 for lemmy.ml and now I can use it.

My suspicion is that nginx is misconfigured and not listening via IPv6. Or maybe the AAAA record is pointing to the wrong IPv6 address.