No description
Find a file
2026-01-12 23:27:21 +01:00
README.md Edit README.md 2026-01-12 23:27:21 +01:00

On some instances, there might be the wrong ip-address shown in https://yourdomain.com/settings/admin/logging when a login failed. This is either caused by a missing trusted_proxy in Nextcloud or caused by ipv6 not being disabled correctly or caused by the docker network not being configured correctly for ipv6. Follow these steps to resolve it:

  1. First, check the admin overview in https://yourdomain.com/settings/admin/overview if there is an ip-address shown as brute-force throttled, that should be added to the trusted_proxies list. If so, you can add it with sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ config:system:set trusted_proxies 2 --value="ip.address.that.is.shown" - of course you need to adjust ip.address.that.is.shown to the one that is shown in the admin overview. After a reboot of the Nextcloud container, there should not be any further throttling and the correct ip-address should be logged in the Nextcloud logs when login fails. If that should not be the case, see below:

If the above is not successul, you can now try to correctly configure the docker network for ipv6:

  1. Stop your containers from the AIO interface
  2. Enable ipv6 in your docker daemon if not already done by following https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md
  3. After the docker daemon started correctly run sudo docker network disconnect nextcloud-aio nextcloud-aio-mastercontainer to disconnect the mastercontainer from the nextcloud-aio network.
  4. now remove the nextcoud-aio network by running sudo docker network rm nextcloud-aio
  5. Then run sudo docker network create nextcloud-aio in order to recreate the nextcloud-aio network
  6. Finally run sudo docker network connect nextcloud-aio nextcloud-aio-mastercontainer to connect the mastercontainer to the network again.
  7. At last, open the AIO interface and start your containers again
  8. Now when failing a login, the correct remote ip-address should be logged.
  9. If still not the correct ip-address should be logged, feel free to create a new discussion here: https://github.com/nextcloud/all-in-one/discussions/new?category=questions