Closed maviterlikli closed 3 months ago
Hello maviterlikli,
Thank you for reaching out to Lens support!
Thank you for reporting a bug.
We are working on your issue. Stand by for further updates.
Best Regards, Tikhon Kudinov Lens Support Engineer Mirantis, Inc
Hello maviterlikli,
Did you try clicking "web browser"? It should open a page for activation. After activating, Lens should open successfully.
Best regards, Anton Nos Software Engineer Mirantis, Inc.
I did it in several other installations. It did not open a browser page. I have just retired it with Firefox and Chrome as the default web browser.
Please follow the instructions.
Please take a screenshot or copy everything you see in the console.
Okay. With the console, I was able to debug it. It gave me my local IP as "27.0.0.1" and the connection failed to that IP since it was wrong. My /etc/hosts file has the "127.0.0.1" as "27.0.0.1". So a human error. Right now, calls are working, and I have been able to log in to my Lens account.
I am really sorry about the inconvenience since I was the root cause. If you need anything, I can help you.
No worries! I am glad that the problem is solved. Don't hesitate to contact support if you have any issues.
Best regards, Anton Nos Software Engineer Mirantis, Inc.
I can't click anything.
I'm pretty pissed off. Why? When 5-10 things fail and one of them is just a simple dashboard... it's a pain in the ass.
Now I will have to wait for 2 types of answers: 1 - The one they never answer 2 - The one they tell you to restart, reinstall or put n commands
It's unfortunate.
First of all, Drakgoku, they are not here to solve your problems, but to make their software better while solving issues that users face. This is how opensource software works. The other best side of opensource is you do not have to use it.
Secondly, all the process that you whine is to eliminate stupid errors and to make sure the issue is isolated to the software. So, rebooting, restarting, etc is essential. As you can see in my case the error is caused by MY wrong entry in the local DNS server. So nothing related to the Lens software. This might be your case as well. If you wish to check simply run 'nslookup localhost' at any terminal. The debug console in mention will also solve most of the issues that are not related the software.
Lastly, if you cannot found any other issues in your system, and if you can isolate the issue, I am pretty sure they will be happy to help as long as you provide them with good input. Otherwise, it is a witch-hunt.
Please remember that, this is not a paid software support center. This place is for open source issue submission.
We are going to differ quite a bit.
First
they are not here to solve your problems
I would like my argument not to be trivialized with your argument when this is a Lens problem and known from what I have seen. Google: Lens stuck on desktop
The other best side of opensource is you do not have to use it.
Correct, that's why I use helm, as the documentation specifies. https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/
I just tried to try other solutions and they recommended Lens. It could have been chips, but it was Lens.
Second
all the process that you whine is to eliminate stupid errors and to make sure the issue is isolated to the software. So, rebooting, restarting, etc is essential.
I have reinstalled 5 times, none of them worked.
First run I don't put everything because there are things like keys and others that I don't want to be seen.
Only reopen
I know it's an opensource and the limitation of resources to solve the problem. I'm aware.
My problem is that it doesn't stay stuck when I try to activate it in the product. When I turn on Lens (double click on the icon) it makes it look like it's loading and when I try to select something I can't. That is, I can't click on anything.
@drakgoku I think your bug is a new one, I haven't seen this one before (e.g. UI completely stuck in this screen). Does any of the application menus work, like showing About lens, opening preferences or the license?
No, no matter what I do, nothing works. I've seen this: https://recoverit.wondershare.com/computer-problems/windows-10-stuck-on-welcome-screen.html But I'm not going to lie to you, I don't plan on using any of the commands it says.
I'm not going to touch anything about disabling the "Credentials Manager" or stopping "services" and even less about Credentials and "sfc /scannow chkdsk c: /f /r" is a huge nonsense. It only verifies the integrity of Windows system files, repairs corrupted or damaged system files, focuses on critical Windows files.
I'll continue this here: https://github.com/lensapp/lens/issues/8089
Describe the bug When Lens is launched, the "Welcome to Lens" screen appears. However, when "New to Lens" or "Already have an Lens ID" is clicked it is stuck on "Activating Lens Desktop".
To Reproduce Steps to reproduce the behavior: Note: I do not think it will be reproducible in any environment.
Expected behavior It should be able to log me in
Screenshots
Environment (please complete the following information):
Logs: When you run the application executable from the command line you will see some logging output. Please paste them here: I have run lens-desktop with DEBUG=true. Logs are too long I am adding as file. LensDebugLog.txt
Kubeconfig: I have removed every kubeconfig from Lens. The issue persists.
Additional context I have tried several things without any success.
apt purge
.~/.config/Lens
and~/.k8slens
and deleted~/.kube/config
.