Netbox configuration with Real IP instead of reverse-proxy IPs #16362
Replies: 2 comments
-
Are you sure? Run |
Beta Was this translation helpful? Give feedback.
-
I'm unsure which logging you are referring to. But here are my tips anyway: These are for getting Nginx to log client source IPs in access.log: /etc/nginx/conf.d/logging.conf
and then add these in /etc/nginx/sites-available/netbox
This is also for /etc/nginx/sites-available/netbox, in the
(If using uWSGI (and Works fine with AWS ELB doing source NAT in front of Nginx on NetBox server. |
Beta Was this translation helpful? Give feedback.
-
Dear NetBox Support Team,
I hope this message finds you well.
I need help configuring NetBox to display real client IP addresses in the access logs instead of the IP address of our reverse proxy. Our reverse proxy is set up to forward the x-forwarded-host, x-forwarded-proto, and x-real-ip headers. However, NetBox does not seem to log these headers correctly.
Could you please provide guidance on the necessary configuration changes in NetBox to ensure it logs the real client IP addresses? Any insights or documentation would be greatly appreciated.
Netbox version 3.7.2
Thank you in advance for your support.
Beta Was this translation helpful? Give feedback.
All reactions