Keep getting invalid username or password on fresh install #565
Comments
|
The default username is admin and password is Harbor12345, while using these what does the log for harbor core say? The log output you posted are not relevant for the login process. |
|
Hi I used the default username and password. This is the logs from harbor core |
|
I can confirm this issue, I installed the chart v1.3.2 with default username/password and I'm getting "Invalid user name or password." error |
|
I can confirm it too. I installed with helm chart version with image: goharbor/harbor-core:v1.10.2 and can not login to Harbor with default password |
|
This error is security-related, so it's designed not to reveal too many details. |
|
I found this article on resetting the harbor admin password from psql which might be helpful |
|
Removing the double quotes from harborAdminPassword: "Harbor12345" fixed the issue for me. |
|
Quotes in yaml are ignored |
|
related: goharbor/harbor#12423 I was able to log in when forwarding the main service but not when using the |
|
I had this issue because I didn't add the protocol to |
|
Gosh, I spend a day fixing that password issue. |
|
I had a same issue. |
|
I don't understand the relation between the admin password and the |
|
I also got the same issue with GKE installation. additional info:
|
|
Accessing harbor-core container and seeing the HARBOR_ADMIN_PASSWORD I saw the current admin password: bitnami So try admin/bitnami |
|
Same problem with Kubernetes 1.22.8 on Digital Ocean managed k8s. I installed the Helm chart for Harbor (not the Bitnami one), used |
|
Ident problem, I deploy with helm and use a values.yaml with harborAdminPassword: d3vH8wt7hGQirPj, later to deploy and I get secret with: kubectl get secrets -n harbor-system harbor-core -o jsonpath="{.data.HARBOR_ADMIN_PASSWORD}" | base64 -dOUTPUT: I get same value that harborAdminPassword so when try to connect via web I'm getting "Invalid user name or password." error. |
|
Please check the logs of your browser, do you get a 405 Method not allowed? I got that for the url I fixed it by adding another Route to my Traefik IngressRoute: apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
name: registry.example.com
namespace: harbor
spec:
routes:
- kind: Rule
match: Host(`registry.example.com`) && PathPrefix(`/`)
priority: 1
services:
- kind: Service
name: harbor-portal
namespace: harbor
port: 80
- kind: Rule
match: Host(`registry.example.com`) && PathPrefix(`/c/`)
priority: 10
services:
- kind: Service
name: harbor-core
namespace: harbor
port: 80
- kind: Rule
match: Host(`registry.example.com`) && PathPrefix(`/api/`)
priority: 10
services:
- kind: Service
name: harbor-core
namespace: harbor
port: 80
- kind: Rule
match: Host(`registry.example.com`) && PathPrefix(`/service/`)
priority: 10
services:
- kind: Service
name: harbor-core
namespace: harbor
port: 80
- kind: Rule
match: Host(`registry.example.com`) && PathPrefix(`/v2/`)
priority: 10
services:
- kind: Service
name: harbor-core
namespace: harbor
port: 80
- kind: Rule
match: Host(`registry.example.com`) && PathPrefix(`/chartrepo/`)
priority: 10
services:
- kind: Service
name: harbor-core
namespace: harbor
port: 80
tls:
certResolver: letsencrypt-prod |
I was able to log back in with the default password by restarting Harbor ( via docker-compose down then up ) |
The error here happened on K8S (the OP mentioned AWS and GKE), not Docker. If using docker-compose it would be very straight-forward. |
|
Shoutout to #565 (comment) for fixing this issue for me. So it seems like Harbor is an SPA that tries to connect directly to harbor-core instead of proxying requests through Maybe this should get added to the documentation for use with Helm charts? |
Can you explain it to me |
hey, this works for me.... at the externalURL field replacing the value with internal/external IP or hostname of your loadbalancer (when you use 'proxy' conf). thank you! |
|
@darthguinea proposed to not go through port-forward which result in a 405 error. See here: #485 A quick summary for the one using helm chart on localhost: Here is the helm configuration I used: expose:
type: loadBalancer
ports:
httpPort: 80
tls:
enabled: falseThen go to your Quick comment for the Harbor team, you guys could add a comment in your documentation for this issue ... spending a few hours to just enter the UI can be a bit a frustrating 😄 |
|
|
I was doing am on-premise install, where I had explicitly disabled TLS: My work-around was to update the "externalURL" setting and use the "http" protocol. This allowed me to login. Hope this helps |
|
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. |
|
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue. |
and others
I have been trying to install harbor on AWS and GKE and each time , I am not able to login using the default password. Im not sure if this is a bug
version is v1.10.1
This is the log from the database
and this is the log from harbor core
This works when I use docker compose but not Kubernetes. Please advise
Thanks
The text was updated successfully, but these errors were encountered: