Skip to content
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

Pass through real client IP address for JupyterHub #205

Open
rkevin-arch opened this issue Nov 28, 2020 · 0 comments
Open

Pass through real client IP address for JupyterHub #205

rkevin-arch opened this issue Nov 28, 2020 · 0 comments

Comments

@rkevin-arch
Copy link
Member

When testing something on Galaxy I saw stuff like:

[I 2020-11-28 09:39:18.176 JupyterHub log:174] 200 GET /hub/spawn ([email protected]@10.0.0.118) 29.21ms

It thinks I logged in from the IP address 10.0.0.118, which happens to be star4, where the nginx ingress is running. Ideally, we want to expose the client's IP address for logging purposes (and maybe to blacklist certain IP ranges in the future if we see abuse of our servies).

Apparantly this is an issue on Flock as well, even if we aren't using an ingress (but that's because it runs autohttps (traefik) to deal with https traffic, which acts like an ingress anyway):

[I 2020-11-28 09:48:12.364 JupyterHub log:174] 200 GET /hub/spawn ([email protected]@10.0.0.110) 21.29ms

See also: kubernetes/ingress-nginx#6163

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant