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
Is the IP block timeout config hardcoded or configurable? If configurable, my apologies, could you point me to the setting location?
Asking because when running in docker, lazylibrarian sees all source ip's as that of the nginx reverse proxy container, so if one user logs in with a bad password, it bans the nginx ip, meaning no one can login. Would enabling the http proxy tick box resolve this, or is there a way to have lazy librarian respect the X-Forwarded-For headers?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Is the IP block timeout config hardcoded or configurable? If configurable, my apologies, could you point me to the setting location?
Asking because when running in docker, lazylibrarian sees all source ip's as that of the nginx reverse proxy container, so if one user logs in with a bad password, it bans the nginx ip, meaning no one can login. Would enabling the http proxy tick box resolve this, or is there a way to have lazy librarian respect the X-Forwarded-For headers?
Thanks in advance.
The text was updated successfully, but these errors were encountered: