-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
[FEAT] Nginx log with real client IP #229
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
The container will already do this, the issue will be your host ke your proxy that is stripping that data. For example on Synology boxes you have to adjust iptables to enable it. |
Hi j0nnymoe, I noticed env var APP_PROXIES, don't know if thats what you mean, eitherway I'm setting it and it's only helping with Audit Log page. Please, let me know if there is any doc / article I can use. Thanks. |
Without knowing your setup, I'm just making assumptions but this was the specific thing I was speaking about for Synology https://www.pedrolamas.com/2020/11/04/exposing-the-client-ips-to-docker-containers-on-synology-nas/ |
That worked for me. Hosting on Azure App Services, when I added the Env Variable "APP_PROXIES=*", I'm now getting client IPs in the audit log. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is this a new feature request?
Wanted change
Bookstack container also provides a web server powered by nginx. However its access logs shows the ip address of the reverse proxies in front of it. It would be much better if there were a way to provide the trusted proxies, so nginx logs the client IP.
Reason for change
The way it is, nginx is logging the IP of reverse proxy in front of the docker, not the real client IP.
Proposed code change
No response
The text was updated successfully, but these errors were encountered: