You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I was recently informed that the mlmym I'm hosting for my site (https://mlmym.lemmy.dbzer0.com/) is intermittently failing and I find that its logs are showing a ton of rate_limit_error. I found #92 here where you suggested to check nginx, but mine has no rate limits. I also increased the rate limits on the lemmy instance itself to no avail.
The problem is I don't even know which endpoint is causing these rate limits. Is there a way to figure out how this is being caused?
Also note that the other frontends don't experience this issue
The text was updated successfully, but these errors were encountered:
Edit: this doesn't seem to be the solution, as I'm still getting rate limit errors. I'll still leave it up in case it helps anyone, though.
I don't know if this is a solution, but I added mlmym to the same docker network as my Lemmy stack and so far, after around 24 hours, I don't have any rate limit errors.
I have two separate Docker Compose files (managed by Dockge).
The Lemmy stack has this at the top, above the "services":
networks:
lemmy-static:
external: true
and then each service has the following:
networks:
- lemmy-static
For the mlmym stack, I can get away with just:
networks:
lemmy-static:
external: true
You may have to create the docker network "lemmy-static", assigning it a static IP, gateway, etc.
This may or may not be the "right" way to do it, and I don't claim to be an expert.
I've only observed it working for 24 hours, so this might not be a good long term solution. Hope it helps, though.
Hey, I was recently informed that the mlmym I'm hosting for my site (https://mlmym.lemmy.dbzer0.com/) is intermittently failing and I find that its logs are showing a ton of rate_limit_error. I found #92 here where you suggested to check nginx, but mine has no rate limits. I also increased the rate limits on the lemmy instance itself to no avail.
The problem is I don't even know which endpoint is causing these rate limits. Is there a way to figure out how this is being caused?
Also note that the other frontends don't experience this issue
The text was updated successfully, but these errors were encountered: