-
Notifications
You must be signed in to change notification settings - Fork 767
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
Invalid user name or password #75
Comments
Check the logs of Harbor core. |
Hi @ywk253100 , there is no new logs after I click LogIn.
I got the login response in below.
BTW, I modify the portal & registry service from ClusterIP to NodePort |
How about the logs of nginx? |
any solution? I met this issue, too. |
@aaronnew2018 Are you using |
@ywk253100 yes, I was using NodePort for Harbor-Portal, and the curl as below:
Loading...
<script type="text/javascript" src="runtime.a66f828dca56eeb90e02.js"></script><script type="text/javascript" src="scripts.70b8b612aef2adc60282.js"></script><script type="text/javascript" src="main.7fa8cf5667e763a02956.js"></script>
|
What is the version of Harbor chart that you are using? |
@ywk253100 the dev version in harbor-helm master branch. The same logs as above bro. : Request URL: https://repository.rhinopithecus.club/c/login |
Can you show me the logs of |
I'm seeing the same issues where after deployment, I cannot log in. I've included the logs below but they don't offer much. I've also attempted the Core logs:
Portal logs:
|
@stevesloka Seems the request is not received by Harbor Core, can you check the debug console of browser and check that the request is sent out. And check the logs of ingress controller or nginx(if you use NodePort). For the chart on 0.3.0 branch, you must run The images used by chart of 0.3.0 branch are Harbor 1.6.0, they are same with the online/offline package of version 1.6.0. And the chart of master branch is using the dev images. They are changed by code merging. |
I have same problems (invalid username or password)
|
@albamc How about the requests sent to backend? You can find them in the |
same issue here as well. |
same issue core logs:
|
|
@andreiapostol22 @silentdark @ywk253100 |
Closing the issue as doesn't get any feedback. |
I would like to see this issue reopened as I am facing the same problem. @ywk253100 see below for the information that you have requested. EnvironmentUsed version of Kubernetes
I have installed all components of Harbor into their own namespace (
Harbor is exposed by my
The new log lines after trying to log in are the following:
But the logs in the browser were the most insightful. It seems like neither the And I discovered the following errors in the console: Hope this helps and the issue can be fixed soon! |
my expose type is nodePort. modify the values.yaml file, "externalURL: https" change to "externalURL: http" before: externalURL: https://10.240.11.10:30002 |
also seeing this, if I reach by the load balancer ip i can log in, though it shows the certs are bad, if i reach via my ingress (which I setup myself, not via the values.yaml) i cannot log in. it would have been nice if there had been a solution posted on this thread, seems like its probably just a setting that's blocking a manually setup ingress |
After helm install XXX, and wait for all pods running.
I enter the portal using default username/password ( admin/Harbor12345), I got "Invalid user name or password".
I have no idea why I cannot login.
Note: I had checked Harbor12345 is defined in secret
The text was updated successfully, but these errors were encountered: