bruteforcesettings
bruteforcesettings copied to clipboard
Add whitelisted IP via hostname to support dyndns / dynamic IP address scenarios
It might be useful to add an IP to whitelist based on a domain name. Think about the following scenario:
The user want's to whitelist connections from his home network ( = his public IP address). He already has a dyndns service running like eg. demouser.duckdns.org. This domain will resolve to his public IP.
It'd be nice if the user could add this domain to the whitelist which then gets (periodically) resolved to the wished IP.
This is probably pretty low on priority, but I wanted to mention the idea 😊
Android app is forcing the traffic threw WAN and not LAN. So I got banned very often (with failed logins). I can´t define a dynamicIp ( using DynDNS). So it could be useful to define a dynamic IP to whitelist until the android app can using local area network for the connection to nextcloud (isn´t already developed).
Cheers.
+1 to adding ability to allow by a domain name. Unfortunately due to the number of devices regularly checking in for caldav/cardav/webdav as well as via web access it is triggering the brute force app to slow us down. 1 of the apps on my phone needs to access specific files on my server via webdav access and always returns a timeout error whenever I am on my home network. If I switch to using mobile phone tethering it updates in microseconds. My server is on a cloud with a permanent IP address but my home access is via a dynamically assigned IP address. For other services to access services on my home network I have a script which detects any change to my home IP and it updates a sub-domain address on my DNS provider.
Any update on this? This is a dearly needed feature on my side. For my private instance, as well as for our customers.