-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Issue with SBOM generation in Harbor v2.11.0 when using external Reverse Proxy (HTTP 404) #20565
Labels
Comments
To solve this issue, the sbom.go should use the internal URL to generate SBOM, the internal URL always starts with |
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 11, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
5 tasks
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 12, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 12, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 12, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 12, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
5 tasks
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 12, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 12, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 14, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 14, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
to stonezdj/harbor
that referenced
this issue
Jun 14, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
stonezdj
added a commit
that referenced
this issue
Jun 14, 2024
fixes #20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
chlins
pushed a commit
to chlins/harbor
that referenced
this issue
Jun 17, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
mohamedawnallah
pushed a commit
to mohamedawnallah/harbor
that referenced
this issue
Jul 2, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
mohamedawnallah
pushed a commit
to mohamedawnallah/harbor
that referenced
this issue
Jul 2, 2024
fixes goharbor#20565 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue:
The new SBOM generation feature in version 2.11.0 uses the external URL, leading to 404 errors due to the reverse proxy configuration.
Suggested Fix:
I recommend that the internal server name be used for SBOM uploads like other internal communications to avoid this issue. This would ensure consistency and prevent misdirected requests that result in 404 errors (and connections failures when calling external services).
Question:
Is there a way to configure Harbor to use the container internal server name instead of the external URL when uploading SBOM results?
Thank for your great work and for looking into this issue. I appreciate any guidance or updates you can provide.
Best regards,
Oliver
My configuration:
User Access --> https://myrepo.example.com (HTTPS)
|
External Nginx Reverse Proxy --> https://internalserver.example.local (HTTPS)
|
Harbor by docker compose
In version 2.10.x, everything functions as expected, including upload of vulnerability scans.
However, in version 2.11.x, the new SBOM generation feature seems to be mistakenly using the external URL (https://myrepo.example.com) for internal communications. This misconfiguration leads to a situation where the external reverse proxy only returns HTTP 404 when accessed from the internal network.
docker compose logs
harbor.yml
I tried to switch my configuration to
external_url: https://nginx:8443
and the sbom upload is working, but docker pull from https://myrepo.example.com failed withdial tcp: lookup nginx on ...: server misbehaving
The text was updated successfully, but these errors were encountered: