macOS app cannot connect to http://localhost:4466/config
See original GitHub issueDescription
MacOS app does not get beyond “Wait while fetching clusters…” state. Cannot connect to http://localhost:4466/config
.
Impact
App seems completely dysfunctional.
Environment and steps to reproduce
- Set-up: macOS Big Sur v11.0.1 (20B29), Headlamp Version 0.1.0 (0.1.0)
- Task: Launched the App
- Action(s):
- Error: See below
Expected behavior
Expected to see some clusters, kubectl context or similar.
Additional information
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (18 by maintainers)
Top Results From Across the Web
Safely open apps on your Mac - Apple Support
macOS alert window: App can't be opened because it was not downloaded from. If your Mac is set to allow apps from the...
Read more >If you can't open an app on Mac - Apple Support
If you recently installed a new version of macOS, some apps may need to be updated or reinstalled. See Install and uninstall apps...
Read more >Open a Mac app from an unidentified developer - Apple Support
In the Finder on your Mac, locate the app you want to open. Don't use Launchpad to do this. Launchpad doesn't allow you...
Read more >If you can't connect to the App Store, iTunes Store, or other ...
Learn what to do if you see a "Cannot connect" message, if an app won't load anything, or if content stops downloading.
Read more >Apple can't check app for malicious software
Control-click the app icon, then choose Open from the shortcut menu. Click Open. The app is saved as an exception to your security...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I identified another reason that caused headlamp to exit. In my kubeconfig I had cluster entries with relative path in
certificate-authority
. The path was relative from my~/.kube
directory. For kubectl that seems to work, but the headlamp backend exits with this error:After I change this to an absolute path, the backend seems to come up.
We will be releasing a new version hopefully today that fixes a bug in the server start up. Hopefully this will fix your issues, but if not, I will ask you to please provide more information afterwards. Stay tuned!