-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config 'trusted_proxies'. Allow networks with CIDR #6550
Comments
This missing feature is quite annoying with docker swarm mode, since all logins get delayed because the brute force detections only sees the proxy which has a dynamic ip address |
I stumbled to this same problem on docker/traefik/letsencrypt -combination |
I have the same problem (docker-compose/traefik/letsencrypt) - and we're not the only ones: nextcloud/docker#294 |
Any news on this? |
We're also running into this issue currently. Any news? |
Seems this is not the case. I still face this issue, too. I had no time to work around it, though. My idea: Starting a sidekick container on proxy bootup to alter the NC config entry. Just wondering if this is a secure way to approach the issue... |
In addition, If you are using Kubernetes I would think of using ConfigMaps/Secrets to populate your NC config at start time. |
Steps to reproduce
Expected behaviour
The real IP should be logged.
Actual behaviour
The IP of the reverse proxy is logged
Server configuration
Operating system:
Official docker-image
Web server:
Official docker-image
Database:
MySQL
PHP version:
Nextcloud version: (see Nextcloud admin page)
12.0.2
Where did you install Nextcloud from:
Docker
Signing status:
Signing status
We are using Rancher in our environment. In front of nextcloud is an nginx reverse proxy. In rancher, any container get a random IP from the internal rancher-network 10.42.0.0/16. If the reverse proxy will be restarted, the container get a new random IP from 10.42.0.0/16.
Is it possible to allow in the config 'trusted_proxies' whole networks in the format 10.42.0.0/16? Currently I would have to write all IPs from 10.42.0.0/16 in the array and this is too much.
The text was updated successfully, but these errors were encountered: