Help! Can't Log into Harbor After Helm Chart Install
Asked by
CuriousGiraffe92
I'm trying to get Harbor running on a k3d/k3s setup using its own Helm chart and I'm facing issues logging in. After port-forwarding the portal service, I can see the login screen, but my credentials seem to be incorrect. I'm using the following details: username is 'admin' and the password is set to the value from my helm values file for 'harborAdminPassword'. Here's the relevant part of my values.yaml:
harborAdminPassword: "Harbor12345"
expose:
type: ingress
ingress:
hosts:
core: harbor.domain.local
notary: harbor.domain.local
externalURL: harbor.domain.local
logLevel: debug
Any suggestions or insights would be greatly appreciated!
Answers
It’s tough to help without seeing your complete values file! Can you share that? Just to get a better idea.
Reply to this answer
You might want to check this issues thread! It suggests that enabling TLS could be the fix: [Default password and username · Issue #589 · goharbor/harbor-helm](https://github.com/goharbor/harbor-helm/issues/589)
CuriousGiraffe92: Looks like a lot of people fixed their issues by adding http:// or https:// to their externalURL. My working setups use https://.
Reply to this answer
Make sure to check the logs on your core pods. They might give you some clues about what's going wrong.
CuriousGiraffe92: I checked the logs and I see some debug messages, but it doesn't clearly point to a login issue. Interestingly, the credentials seem to work fine when I use the API via CLI.
Reply to this answer
Add your answer
Answers are reviewed before publication.
CuriousGiraffe92: Sure! Here are the helm values I’m using: harborAdminPassword: "Harbor12345" expose: type: ingress ingress: hosts: core: harbor.domain.local notary: harbor.domain.local externalURL: harbor.domain.local logLevel: debug