this post was submitted on 13 Jun 2023
152 points (100.0% liked)

lemmy.ml meta

27 readers
1 users here now

Anything about the lemmy.ml instance and its moderation.

For discussion about the Lemmy software project, go to !lemmy@lemmy.ml.

founded 3 years ago
MODERATORS
nutomic@lemmy.ml
152
lemmy.ml is migrated to a new server (lemmy.ml)
submitted 1 year ago by nutomic@lemmy.ml to c/meta@lemmy.ml
76 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
[–] Catsrules@lemmy.ml 0 points 1 year ago* (last edited 1 year ago) (2 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. I had a few people say turning off IPV6 on their end fixes the 502 Bad Gateway, so it looks like it has something to do with IPV6.

[–] nutomic@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

You are right, I forgot to configure IPv6. Will be fixed shortly.

Edit: Should be fixed now.

[–] techviator@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

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.

@nutomic@lemmy.ml Thanks for upgrading the server!