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.

Sign up for GitHub

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

Jump to bottom

Handling of http status 429 response codes from CT #51

Open
a-schild opened this issue Apr 12, 2024 · 1 comment
Open

Handling of http status 429 response codes from CT #51

a-schild opened this issue Apr 12, 2024 · 1 comment
Labels
question

Comments

@a-schild
Copy link
Contributor

We did migrate back from our own hosted churchtool to ChurchTool.

Since then, the rest api of CT returns a lot of 429 errors (Too many requests)
Even with caching enabled we get these errors, and then the logins fail in the LDAP.

Any way to improve handling of this?
@milux
Copy link
Owner

milux commented May 10, 2024 •
edited
Loading

Sorry, cannot reproduce.
We don't see any 429 errors in our instance and have successfully migrated some weeks ago.
Are you using the very latest version of ctldap?
How many users and groups do you have in your instance? Are you using default caching options (defaults to CACHE_LIFETIME_MS=300000) or have you increased the frequency?

@milux milux added the question label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@milux @a-schild