You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can happen that you face performance issues with Nextcloud, like having to wait something like 60 or more seconds until the Nextcloud web interface loads. See the steps below how to debug this. Additionally see #1335 for general recommendations.
A first step would be to temporarily disable Nextclouds bruteforce protection and ratelimit protection by running sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set auth.bruteforce.protection.enabled --type bool --value=false
and sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set ratelimit.protection.enabled --type bool --value=false and check if it fixes the performance problems.
If that should be the case, you are likely facing problems due to Nextclouds own bruteforce protection or ratelimit protection limiting the requests.
Since the above setting is obviously not secure, you should next enable the protection again by running sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set auth.bruteforce.protection.enabled --type bool --value=true
and sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set ratelimit.protection.enabled --type bool --value=true
Afterwards, try to log in with a random account and random password into Nextcloud from an icognito tab from the same device and check in the server logs https://yourdomain.com/settings/admin/logging which ip-address gets logged (usually the public ipv4-address or ipv6-address of your device). If it should be an unexpected private ip-address, you have likely found the culprit. See #2045 how to proceed.
Afterwards, the correct ip-address should usually be logged and the ratelimiting and bruteforce protection only happen for requests that actually trigger it. If it should still be slow without disabling the bruteforce and ratelimit protection, feel free to create a new discussion here: https://github.com/nextcloud/all-in-one/discussions/new?category=questions
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It can happen that you face performance issues with Nextcloud, like having to wait something like 60 or more seconds until the Nextcloud web interface loads. See the steps below how to debug this. Additionally see #1335 for general recommendations.
A first step would be to temporarily disable Nextclouds bruteforce protection and ratelimit protection by running
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set auth.bruteforce.protection.enabled --type bool --value=false
and
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set ratelimit.protection.enabled --type bool --value=false
and check if it fixes the performance problems.If that should be the case, you are likely facing problems due to Nextclouds own bruteforce protection or ratelimit protection limiting the requests.
Since the above setting is obviously not secure, you should next enable the protection again by running
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set auth.bruteforce.protection.enabled --type bool --value=true
and
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set ratelimit.protection.enabled --type bool --value=true
Afterwards, try to log in with a random account and random password into Nextcloud from an icognito tab from the same device and check in the server logs
https://yourdomain.com/settings/admin/logging
which ip-address gets logged (usually the public ipv4-address or ipv6-address of your device). If it should be an unexpected private ip-address, you have likely found the culprit. See #2045 how to proceed.Afterwards, the correct ip-address should usually be logged and the ratelimiting and bruteforce protection only happen for requests that actually trigger it. If it should still be slow without disabling the bruteforce and ratelimit protection, feel free to create a new discussion here: https://github.com/nextcloud/all-in-one/discussions/new?category=questions
Beta Was this translation helpful? Give feedback.
All reactions