"remoteAddr" logged as SWAG container's IP with SWAG/fail2ban/Nextcloud setup

The nginx config’s we supply within SWAG and Nextcloud are pre-configured for it.

I followed the instructions at Install Docker Engine on Debian | Docker Documentation specifically for debian systems and for stability.

Current version: 20.10.7, build f0df350

Is the only configs to edit thus at:

SWAG:

  • /config/nginx/proxy-confs/nextcloud.subdomain.conf

NEXTCLOUD:

  • /config/www/nextcloud/config/config.php

whereafter the remote_ip (or client_ip) is usually referenced correctly within nginx & nextcloud logs?

@peek Did you ever solve this? I’m having a similar problem with the IP always being the IP of the Docker network: How do I handle this scan attack? - LSIO Discussion / Container Support - LinuxServer.io