-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Real IP from AWS to nginx proxy to gitlab's nginx-proxy #1223
Comments
Ah.. surprisingly, I was able to make it work... I also added inside gitlab container's nginx.conf (also with main nginx proxy container)
and with main nginx proxy gitlab.conf
Now it works as I expected it... but I had to do this hard coding edit into a a live gitlab container... Is there anyway this can be done upon first run of the container? |
FYI, Could be useful to others. I was successful setting this up with config |
Note: this assumes your nginx is running natively or using --net=host (in addition mine is behind AWS ELB) |
This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions. |
Hey guys,
Just need a bit of help, I've struggling with this for hours now... the thing I need to send the real client IP address...
So, I used the basic nginx container with
--net=host
I also followed for the AWS ELB:
https://easyengine.io/tutorials/nginx/amazon-elastic-load-balancer-forward-real-ip/
Now I'm able to verify that the nginx is able to capture the actual client IP address, when I enable
proxy_set_header X-Forwarded-Host $remote_addr;
However, how do I pass this IP to gitlab? cause what it currently gets is the private IP address of the docker host where nginx proxy is running.
Anyone encountered the same issue, and how were you able to solve this issue?
This is my config for
gitlab.conf
Thanks,
The text was updated successfully, but these errors were encountered: