I would like to understand the reason for this behavior.
From my experience, when I log in to my office network over the LAN, my system uses one IP address. If I then take the same computer (without logging out) to another location, such as a presentation room, and connect to Wi-Fi, the network assigns a different IP address.
In this scenario, Fail2Ban detects the same login activity coming from multiple IP addresses and treats it as suspicious behavior, resulting in the IP address being banned.
This issue occurs on DigitalOcean, my local server, and AWS. However, this does not happen on Frappe Cloud, where my IP addresses are not blocked.
Could you please explain why Fail2Ban blocks the IPs in DigitalOcean, local servers, and AWS, but not in Frappe Cloud?
What configuration or security mechanism causes this difference in behavior?