Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A lot of "rate_limit_error" #109

Open
db0 opened this issue Aug 22, 2024 · 1 comment
Open

A lot of "rate_limit_error" #109

db0 opened this issue Aug 22, 2024 · 1 comment

Comments

@db0
Copy link

db0 commented Aug 22, 2024

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

@etymotic
Copy link

etymotic commented Oct 10, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants