Closed LePresidente closed 1 year ago
Looks like this is unlikely unless goharbor uses a custom nginx build on proton.
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
Hello, any update about this?
Still waiting on upstream, looks like it will be done soon though
Tested in 2.8.1
May 16 11:25:57 172.24.0.1 proxy[1160]: [REDACTED] - "GET /api/v2.0/users/current HTTP/1.1" 401 62 "https://[REDACTED]/account/sign-in?redirect_url=%2Fharbor%2Fprojects" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 Edg/113.0.1774.42" 0.005 0.004 .
correct external IP is shown now when adding the above options to nginx.conf
This can be closed
Expected behavior and actual behavior: When running goharbor behind a reverse proxy, it shows the incorrect ip (docker ip) in the logs instead of the external ip
Steps to reproduce the problem: Just run the system behind any reverse proxy will result in the following logs
Versions: Please specify the versions of following systems.
Additional context:
This can be fixed in goharbor/nginx-photon by adding the following to the server block and adding the following nginx module http_realip_module