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
Cannot login to docker 400 Bad Request #1710
Comments
I did some further digging: Via /service/token?account=[username]&offline_token=true&service=harbor-registry&client_id=docker i can get a token. The logs during this on harbor-core:
|
Same error here. I'm my case I'm able to run |
I never tested it until now. But in my case it fails as well:
|
Hi @jonsch318 , Traefik ingress is not tested. Have you got a chance to try nginx ingress? |
also, please check this issue #582 for information of using Traefik with Harbor-helm |
Unfortunately I am stuck with traefik. But it shouldn't matter since all Authorization headers get forwarded successfully (since it would say 401 otherwise i think). In version v1.13.2 the issue still persists |
I switched from Node-Port mode to Ingress with Nginx Ingress Controller and
It worked fine.... I think the issue has to be related somehow with the
FQDN domain rule matching at nginx level
But I can't confirm that....
El sáb, 24 feb 2024 a las 12:45, Jonas Schneider ***@***.***>)
escribió:
… Unfortunately I am stuck with traefik. But it shouldn't matter since all
Authorization headers get forwarded successfully (since it would say 401
otherwise i think).
In version v1.13.2 the issue still persists
—
Reply to this email directly, view it on GitHub
<#1710 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLBWYX26KOLAO24DUZCKRDYVHGRHAVCNFSM6AAAAABDOQ2BQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGMZTKOJSGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
unfortunately even with a nginx intermediate proxy like @TheMatrix97 it is not working. As well as when i use nginx as deployed in cluster ip expose mode and just port-forward to it. It is a underlying issue of harbor core as i think |
I just updated to 1.14.1 helm chart and Harbor 2.10 and the problem still persists |
I got the same issue with latest helm chart Harbor 2.10 and traefik |
Just installed Harbor and now seeing this same issue. |
Hello,
In the last week i tried deploying harbor via helm ready to be in HA (not yet: still replica=1).
Until now i have finally been able to access the harbor ui and create a user.
But now when i try to
docker login registry.[tldomain]
i get prompted to enter username & password and after that:Harbor environment: Many different configs tried
Version v2.10.0-6abb4eab
Traefik ingress with custom IngressRoute
internalTLS: enabled (when disabling it does not work either) using custom certs provided by certmanger.
postgres: external (no logs indicate a failure, all permissions granted)
redis: generated looks good
core:
secret: given as existingSecret 16 chars via vault-secrets-operator
xsrf & token tls: generated using helm
jobservice:
secret: given as existingSecret 16 chars via vault-secrets-operator
registry:
secret: given as existingSecret 16 chars via vault-secrets-operator
trivy: disabled
When logging in with
docker login -u [username] --password-stdin registry.[tldomain]
docker never prompts for a passwordWhen logging in with
docker login registry.[tldomain]
i get prompted to enter username&password and thenDuring this deployment/registry-harbor-core does not log anything.
Traefik access logs:
When giving an invalid password
So i know i did not enter the wrong credentials. I it must have something to do with the ingress and http headers.
I'm trying to get more information about the http headers.
This does also not work with podman.
Has anyone encountered a similar problem?
The text was updated successfully, but these errors were encountered: