Impossible to switch off the rate limits

Bug
1

I have self-hosted a vikunja installation v0.24.6. I installed it using Docker Compose, and it works, but occasionally sometimes I get an error 429 “Too Many Requests”. I tried to turn off the rate limit in the config file and added the following lines:

ratelimit:
  enabled: false

In the logs, I saw that Vikunja was using my configuration file.

2025-07-03T12:54:39Z: INFO ▶ 001 Using config file: /etc/vikunja/config.yml

But it did not help. I am still getting 429 error. I have tried to add environment variables to the docker-compose file.

VIKUNJA_RATELIMIT_ENABLED: false

But it also doesn’t help. Please advise.

2

Which route are you seeing the error on?

3

For example, on POST http://127.0.0.1/api/v1/login. Does it matter? My task is to switch off rate limits for all endpoints.

4

There are different rate limits for different parts of the application. Unauthenticated routes (login, register, password reset, etc) have really high rate limits (max. 10 requests per minute per IP) to prevent attackers from checking if an email address is registered and other things. These cannot be disabled.

Usually, 10 per minute is largely enough. How many users do you have?

1 Like
5

I’m running into the same issue during development. As vikunja is running in a local network rate limiting only creates issues. So is there a way to disable it completely?

6

No way to disable this.

What rate limits are you seeing? Why is it different in a local network than when running somewhere in the internet?

7

I’m writing a script that is run whenever i change the source and so it’s loggin in all the time during development. I ran multiple times into rate limits becaufe of that.

The difference in local network traffic is that I don’t need to worry about illegitimate traffic because I’m the only one on the network. The rate limiting is useless for this use case and annoying during development.