-
Notifications
You must be signed in to change notification settings - Fork 150
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
x_forwarded_for header #46
Comments
This is a limitation of netbox-docker, which now uses NGINX Unit. It looks like support for this is simply missing from NGINX Unit: nginx/unit#132. Sorry. |
@bootc Will you update to unit 1.25 to allow this ? |
This needs to be fixed in netbox-docker, not in this chart, so you'd need to ask there. As of the |
Understood. Thanks! |
I've created an issue (in netbox-docker) to update the NetBox Docker image with Alpine 3.15 (released earlier this week) which contains Unit 1.26: netbox-community/netbox-docker#654 |
NetBox 3.2.1 still appears to use Alpine 3.14, so this still isn't fixed. |
Any news? |
We're almost there! The NetBox 3.2.6 container is now built from netbox-community/[email protected] and includes NGINX Unit 1.27.0. In theory you should be able to pass a modified version of |
I haven't been able to make it work :( |
It looks like the current docker images are up to unit 1.32, is this still an issue? |
I haven't tested this, but it should be OK with recent NetBox and the 5.0 chart, but you'll need to override the NGINX Unit configuration in the chart to include the necessary runes to enable it. https://unit.nginx.org/configuration/#ip-protocol-forwarding |
Closing as fixed upstream and proper links for configuration provided. |
Hi bootc , thanks for this helm chart, it works great!
I have a question, though. If I remind correctly, old versions of netbox used to have nginx as a requirement for serving static content, but in this chart I have absolutely no idea how the content is served. I only see some unitd processes:
Anyways, my question is : Is there anyway to make the real client IP appears in the log files for this chart ?
In plain nginx I could just set some parameters and it would work. On this chart I have no idea how to make it work.
Thanks!
The text was updated successfully, but these errors were encountered: