-
Notifications
You must be signed in to change notification settings - Fork 125
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 not forwarded to app container #174
Comments
I had a look into the docker-compose logs again and found something strange that might be a hint. This snippet logs one (and only one) site request. In all lines but one you see the docker-ip (172.17.0.1). In the 5th line suddenly my real IP appears.
But when I use the TorBrowser it looks like this:
Any idea or hint or further question is welcome. Regards, EDIT: this logs come from a setup using interlock 1.1.0 |
Hmm this is odd. I thought we had it setup to pass the real IP. I will see if I can duplicate. |
Hi there!
I use interlock to manage serveral web apps on the same host.
For one app I need the real ip address of the visitor to be passed to the app container. But neither the reverse nginx nor the app container see the real ip. On both I get 172.18.0.1.
As I understand the nginx.conf.template the real ip should be forwarded...
Could it be a bug or is it just bad configured on my side?
Thanks in advance for any hint,
~D
Here's my configuration:
docker-compose.yml
config.toml
nginx.conf.template
https://github.com/ehazlett/interlock/blob/master/docs/examples/nginx/nginx.conf.template.example
The text was updated successfully, but these errors were encountered: