Probably since I’ve updated to server version 34.0.0 (did the update a few days ago, and just noticed the issue today, but then I haven’t used the respective client PC really since then)
Main problem is that desktop client (4.0.7daily (Fedora)) is disconnected, and I cannot connect again:
- From the running client there seems no possibility to do so currently; when I click on the down arrow next to my account name, I see a drop down again with my account and an arrow to the right. When I click on that down arrow, a menu flashes open for a fraction of a second, then both menus close again)
- On starting the client, a login window appears, it opens a browser window to login, but even if I log in there and grant access, the window never closes or logs the client in (when I grant access, the “Authentication required” dialog comes up; when I enter my password there and “Confirm”, the button shows a spinning wheel for ~1 second and then the dialog closes, returning to the “Grant Access” page below without changes there)
For further investigation, I’ve looked at my server. The administration backend under “Security & setup warnings” showed a warning:
Brute-force Throttle Your remote address was identified as x.x.x.x and is brute-force throttled at the moment slowing down the performance of various requests. If the remote address is not your address this can be an indication that a proxy is not configured correctly.
(x.x.x is indeed my current external IP).
The warning has disappeared since however.
In Brute force settings I see
Your current IP address is detected as “x.x.x.x”. This address is currently throttled. Current delay: 1600 ms.
(again, same IP as above).
When I try to enable "Bypass rate limiting for allowed IPs, there is an error message:
Failed to save the rate limit setting.
Is this a known issue? What can I do to further debug (the login problems, whether the brute force stuff is relevant to the problem I don’t know but I thought I’d post it since its something that is also new since NC34)?
