Hello.
After updating to Transmission 3.0 I've started to get this error after Transmission is left running for some time on my NAS. I see that this is an anti-brute force protection (https://github.com/transmission/transmission/pull/371) for the RPC, but I can't find out where these numerous login attempts come from.
Is there a way to log RPC login attempts? E.g. time, username, IP?
Too many unsuccessful login attempts. Please restart transmission-daemon.
Re: Too many unsuccessful login attempts. Please restart transmission-daemon.
I would also be interested in both logging failed login attempts and being able to configure this feature.
Shutting down the interfaces (the lockdown does seem to affect the HTTP interface as well) might be justified in case of a suspected hacking attempt but doing so indefinitely (needing a restart to be able to access transmission) causes way more problem for me than I feel acceptable.
I would prefer having a 5 minutes lockdown but it would be best to have a configuration setting for this.
Shutting down the interfaces (the lockdown does seem to affect the HTTP interface as well) might be justified in case of a suspected hacking attempt but doing so indefinitely (needing a restart to be able to access transmission) causes way more problem for me than I feel acceptable.
I would prefer having a 5 minutes lockdown but it would be best to have a configuration setting for this.