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
It isn't maintainable in the long term to have the nginx IP blocking configuration embedded in the file containing the server/location list. In particular, it would be much easier to integrate with rate limiting #168 and fail2ban if the configuration file was in a dedicated file such as /etc/nginx/conf/ala-geoblocks.conf or similar.
The cue for reforming this (again) was a single IP address that was able to interrupt the ALA infrastructure today.
The text was updated successfully, but these errors were encountered:
It isn't maintainable in the long term to have the nginx IP blocking configuration embedded in the file containing the server/location list. In particular, it would be much easier to integrate with rate limiting #168 and fail2ban if the configuration file was in a dedicated file such as
/etc/nginx/conf/ala-geoblocks.conf
or similar.The cue for reforming this (again) was a single IP address that was able to interrupt the ALA infrastructure today.
The text was updated successfully, but these errors were encountered: