# Cannot login: Too Many Requests

**URL:** <https://help.nextcloud.com/t/cannot-login-too-many-requests/100905>\
**Category:** ℹ️ Support\
**Tags:** bruteforce, bruteforcesettings-app\
**Created:** [December 11, 2020, 10:51am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905 "2020-12-11T10:51:57Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![TomDalla](https://help.nextcloud.com/user_avatar/help.nextcloud.com/tomdalla/32/32074_2.png) [@TomDalla](https://help.nextcloud.com/u/TomDalla)\
**Post date:** [December 11, 2020, 10:51am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/1 "2020-12-11T10:51:57Z")

</div>

I get this error message when I login:

## Too many requests

There were too many requests from your network. Retry later or contact your administrator if this is an error.

 ![image](https://help.nextcloud.com/uploads/default/original/3X/3/e/3e55f48790164b6260bc3a33a3080b7db6330c4b.png)

Running NextCloud 20 on docker (linuxserver/nextcloud) with nginx.  
Nothing particularly helpful in nginx/nextcloud logs.  
How can I reset the “too many requests” check and re-enable login?

---

<div class="post-metadata">

**Author:** ![Kritta](https://help.nextcloud.com/letter_avatar/kritta/32/6_22734026db12803ebb3e059622ac3534.png) [@Kritta](https://help.nextcloud.com/u/Kritta)\
**Post date:** [December 11, 2020, 11:19am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/2 "2020-12-11T11:19:38Z")

</div>

I’m having exactly the same problem on a new install. I’m also using docker and nginx. This happened on my first attempt to log in. However, if I use a VPN I can log in.

---

<div class="post-metadata">

**Author:** ![TomDalla](https://help.nextcloud.com/user_avatar/help.nextcloud.com/tomdalla/32/32074_2.png) [@TomDalla](https://help.nextcloud.com/u/TomDalla)\
**Post date:** [December 11, 2020, 12:27pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/3 "2020-12-11T12:27:29Z")

</div>

A couple hours later it seems to be working again.  
Hopefully the issue doesn’t come back.

---

<div class="post-metadata">

**Author:** ![robi16siv](https://help.nextcloud.com/letter_avatar/robi16siv/32/6_22734026db12803ebb3e059622ac3534.png) [@robi16siv](https://help.nextcloud.com/u/robi16siv)\
**Post date:** [December 11, 2020, 4:18pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/4 "2020-12-11T16:18:29Z")

</div>

Exactly the same problem, newest nextcloud release, jails (FreeNAS), nginx.  
Somebody know how to fix this?

---

<div class="post-metadata">

**Author:** ![Kritta](https://help.nextcloud.com/letter_avatar/kritta/32/6_22734026db12803ebb3e059622ac3534.png) [@Kritta](https://help.nextcloud.com/u/Kritta)\
**Post date:** [December 11, 2020, 8:39pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/5 "2020-12-11T20:39:02Z")

</div>

Mine is still not working the next day. But after 12 hours… it seems to work. This, however, does require a more efficient solution than waiting 12 hours. Looking forward to updates.

---

<div class="post-metadata">

**Author:** ![xavier\_30](https://help.nextcloud.com/letter_avatar/xavier_30/32/6_22734026db12803ebb3e059622ac3534.png) [@xavier\_30](https://help.nextcloud.com/u/xavier_30)\
**Post date:** [December 13, 2020, 11:33am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/6 "2020-12-13T11:33:57Z")

</div>

Same here, not attached to a specific account, get the same answers for all accounts. Works when using a VPN.  
Maybe there is an option somewhere, where we can clear an IP address from this probable security feature.

---

<div class="post-metadata">

**Author:** ![Petr\_Jakes](https://help.nextcloud.com/user_avatar/help.nextcloud.com/petr_jakes/32/32314_2.png) [@Petr\_Jakes](https://help.nextcloud.com/u/Petr_Jakes)\
**Post date:** [December 13, 2020, 1:21pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/7 "2020-12-13T13:21:39Z")

</div>

Same here.  
I was able to login using local IP address without https.  
After it was possible to login using domain name.

---

<div class="post-metadata">

**Author:** ![Timbo](https://help.nextcloud.com/user_avatar/help.nextcloud.com/timbo/32/32492_2.png) [@Timbo](https://help.nextcloud.com/u/Timbo)\
**Post date:** [December 16, 2020, 2:39pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/8 "2020-12-16T14:39:37Z")

</div>

Same here, running nextcloud behind an nginx and after a fresh install.

Solved it by loggin in directly to the http ip of my nextcloud vm and after that, whitelisting my local home ip range under security settings --\> Brute-Force IP-Whitelist.

Only a workaround, but fixed it for the moment.

---

<div class="post-metadata">

**Author:** ![gibikha](https://help.nextcloud.com/user_avatar/help.nextcloud.com/gibikha/32/32133_2.png) [@gibikha](https://help.nextcloud.com/u/gibikha)\
**Post date:** [December 17, 2020, 8:31am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/9 "2020-12-17T08:31:21Z")

</div>

Hi,

I had the same issue, the same erratic behaviour, and then when I looked through the configuration, I noticed that my apache server was listening on both port 80 and 443, which shouldn’t be the case for nextcloud install.

When I disabled port 80 for nextcloud, all was good again, and it was stable.

Try that and and if it works, we can suggest it a documentation update.

-G

---

<div class="post-metadata">

**Author:** ![zenney777](https://help.nextcloud.com/user_avatar/help.nextcloud.com/zenney777/32/32704_2.png) [@zenney777](https://help.nextcloud.com/u/zenney777)\
**Post date:** [December 21, 2020, 8:24pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/10 "2020-12-21T20:24:32Z")

</div>

Hi All, Any luck with the root of the issue, I’m in the same boat

---

<div class="post-metadata">

**Author:** ![benoitdr](https://help.nextcloud.com/letter_avatar/benoitdr/32/6_22734026db12803ebb3e059622ac3534.png) [@benoitdr](https://help.nextcloud.com/u/benoitdr)\
**Post date:** [December 27, 2020, 8:20am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/11 "2020-12-27T08:20:31Z")

</div>

Same problem here, only for 1 user and only from the android client (either from wifi or cellular network).  
Nothing relevant in the log file.

---

<div class="post-metadata">

**Author:** ![Da01W6hwz](https://help.nextcloud.com/letter_avatar/da01w6hwz/32/6_22734026db12803ebb3e059622ac3534.png) [@Da01W6hwz](https://help.nextcloud.com/u/Da01W6hwz)\
**Post date:** [December 28, 2020, 9:02pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/12 "2020-12-28T21:02:33Z")

</div>

Also seeing this on an iOS device, but not Android (or browser based though I’ve not seen anyone complain about this from a browser). If it makes any difference, I am using the Linuxserverio docker image and running NC 20.0.4.

I’m not quite sure what to look for in the logs, but the first seemingly related one looks like this:

```auto
[core] Warning: Login failed: '<user>' (Remote IP: '<ip>')

PROPFIND /remote.php/webdav
from <ip> at <date-time>

```

A couple of those follow by a bunch of:

```auto
PUT /remote.php/webdav/<...>

```

Which l think all correspond to an attempt to upload some photos (manually).

No security or setup warnings in the admin overview.

Has anyone managed to figure out what this is yet or how to work around it before a fix arrives?

---

<div class="post-metadata">

**Author:** ![jotatr](https://help.nextcloud.com/letter_avatar/jotatr/32/6_22734026db12803ebb3e059622ac3534.png) [@jotatr](https://help.nextcloud.com/u/jotatr)\
**Post date:** [December 29, 2020, 6:22pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/13 "2020-12-29T18:22:26Z")

</div>

Hi all,  
I was having the same issue and I believe that it’s because I changed my user password in admin panel and did not update the android app login. I was having repeatedly failed login attempts.

I was able to get rid of the error message by deleting the content of the table "oc\_bruteforce\_attempts " on nextcloud database.  
`DELETE FROM nextcloud.oc_bruteforce_attempts`

You can put a where clause and limit it by IP so that only your login attempts are deleted:  
`DELETE FROM nextcloud.oc_bruteforce_attempts WHERE ip ="X.X.X.X";`

---

<div class="post-metadata">

**Author:** ![alivansheikh](https://help.nextcloud.com/letter_avatar/alivansheikh/32/6_22734026db12803ebb3e059622ac3534.png) [@alivansheikh](https://help.nextcloud.com/u/alivansheikh)\
**Post date:** [December 30, 2020, 12:05am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/14 "2020-12-30T00:05:39Z")

</div>

This solved it for me. thanks!

---

<div class="post-metadata">

**Author:** ![cloo](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cloo/32/16751_2.png) [@cloo](https://help.nextcloud.com/u/cloo)\
**Post date:** [December 30, 2020, 8:02pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/15 "2020-12-30T20:02:35Z")

</div>

My guess the problem is, that after a password change, some app (in my case - android client) bursts attempts to login with the old password, which looks like a brute-force attack for the server, which locks out the IP.  
It was no -docker situation. If it is like I think, a bug should be registered.

Deleting records in oc\_bruteforce\_attempts from database fixes it (untill next password change?). Thanks @jotatr.

---

<div class="post-metadata">

**Author:** ![Da01W6hwz](https://help.nextcloud.com/letter_avatar/da01w6hwz/32/6_22734026db12803ebb3e059622ac3534.png) [@Da01W6hwz](https://help.nextcloud.com/u/Da01W6hwz)\
**Post date:** [December 31, 2020, 6:03pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/16 "2020-12-31T18:03:51Z")

</div>

FWIW there looks to be a new occ command in NC20 to address this without having to jump into sql commands:

security:bruteforce:reset

For the Linuxserverio docker, you’d want to bash into the container:

```auto
docker exec -it <container-name> bash

```

and run the command something like this:

```auto
sudo -u abc php /config/www/nextcloud/occ security:bruteforce:reset <ip>

```

I haven’t been able to confirm if this fixed it yet as the person who was affected by this uninstalled the app and hasn’t yet reinstalled, but I thought I would follow up with this method in case anyone else might find it simpler.

---

<div class="post-metadata">

**Author:** ![zindik](https://help.nextcloud.com/user_avatar/help.nextcloud.com/zindik/32/32788_2.png) [@zindik](https://help.nextcloud.com/u/zindik)\
**Post date:** [January 2, 2021, 7:45pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/17 "2021-01-02T19:45:17Z")

</div>

How did you solved ? We do not need know that you already solved or not. We need to know how did you solved

---

<div class="post-metadata">

**Author:** ![steve4](https://help.nextcloud.com/letter_avatar/steve4/32/6_22734026db12803ebb3e059622ac3534.png) [@steve4](https://help.nextcloud.com/u/steve4)\
**Post date:** [January 6, 2021, 3:07pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/18 "2021-01-06T15:07:50Z")

</div>

Same issue here. I think caused by the latest Android app update. It kept trying to tell me to “Grant Access” even though I’ve used the app on that device for months now. But, even trying web access from my laptop gave the same error so I had initially ruled that out.  
The clues and solution found by @Da01W6hwz proved helpful to me with one nuance I think worth mentioning. In my case, the IP address was 127.0.01 which at first didn’t make sense to me. Then I remembered that my nextcloud is running on apache behind an nginx reverse proxy on the same host. So, all requests appear to come from the localhost regardless of where or what device they actually originated. Hope this helps someone.

---

<div class="post-metadata">

**Author:** ![alexstaj](https://help.nextcloud.com/letter_avatar/alexstaj/32/6_22734026db12803ebb3e059622ac3534.png) [@alexstaj](https://help.nextcloud.com/u/alexstaj)\
**Post date:** [January 6, 2021, 4:05pm UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/19 "2021-01-06T16:05:24Z")

</div>

I deleted everything in the oc\_bruteforce\_attempts table and now it works.

Was there anything in that table that I maybe should not have deleted?

---

<div class="post-metadata">

**Author:** ![peelie](https://help.nextcloud.com/letter_avatar/peelie/32/6_22734026db12803ebb3e059622ac3534.png) [@peelie](https://help.nextcloud.com/u/peelie)\
**Post date:** [March 7, 2021, 11:16am UTC](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905/20 "2021-03-07T11:16:09Z")

</div>

thanks this helped me with this problem

[Next page](https://help.nextcloud.com/t/cannot-login-too-many-requests/100905.md?page=2)
