-
Notifications
You must be signed in to change notification settings - Fork 44
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
Enhancement: use gethostbyname for dynamic trusted_proxies (like php of nextcloud does) #122
Comments
the push daemon doesn't check the trusted proxies itself, it just adds itself to the list of proxies the request has passed trough. |
Here is the error in my docker container:
|
I am facing the same issue. I need gethostbyname() in trusted_proxies for dynamic docker IPs which change on container recreation. Thats currently not possible with notify_push and results in the above error. |
this would be great! |
I would like to see this as well. I am currently in the process of trying to follow this after upgrading to Nextcloud 29. And it feels like it might be a major piece to getting notify_push working within docker |
I recently switched my Docker stacks from static IPs to hostnames, as this is much easier to maintain. Unfortunately, I also realized that push_notify no longer works in this case. |
Hi, I have setup all correctly, but I get:
push server is not a trusted proxy, please add '172.22.1.1' to the list of trusted proxies or configure any existing reverse proxy to forward the 'x-forwarded-for' send by the push server.
As you can see, is 172.22.1.1 a dynamic ip from docker, I use multiple docker-compose files and and multiple networks (dynamic ips), is there any way to dynamically. Setting the ip of this docker network to static would make it less flexible, so something like gethostbyname would be great, if it would work also for notify_push:
nextcloud/documentation#7005 (comment)
The text was updated successfully, but these errors were encountered: