Open deiga opened 8 months ago
The debug message of Strange: no context for ''
is a part of normal loading, so ignore it.
The normal session would produce logs from GIN about any attempt to access it. Like this:
undera@undera-primary:/tmp/downloads$ helm dashboard
INFO[0000] Helm Dashboard by Komodor, version 1.3.3 (b61adf133f639b8bffd43925b5b4b8230c197a26 @ 2023-06-22T08:59:05Z)
INFO[0002] Discovered Checkov version: 2.3.294
INFO[0002] User analytics is collected to improve the quality, disable it with --no-analytics
INFO[0002] Opening web UI: http://localhost:8080
INFO[0002] Updating repository: crossplane
Opening in existing browser session.
[GIN] 2024/03/06 - 18:39:36 | 200 | 5.697657ms | 127.0.0.1 | GET "/"
...
Even 404 would be reflected like this:
[GIN] 2024/03/06 - 18:40:27 | 404 | 7.05µs | 127.0.0.1 | GET "/boo"
[GIN] 2024/03/06 - 18:40:27 | 404 | 5.229µs | 127.0.0.1 | GET "/favicon.ico"
So it looks like your browser hits some other service or proxy instead of local dashboard. Please check that you don't have a proxy preventing you to access local sites.
I can also observe this kind of error when I execute as plugin directly inside the root folder of the project. I still don't know why though or if it is even a proof of something :disappointed: Executing helm dashboard
on any other folder works to me
@alessandrodetta What you see can be explained by this section in old code: https://github.com/komodorio/helm-dashboard/blob/v1.3.3/pkg/dashboard/api.go#L169 . However, it would produce explicit warning in log.
Oh now I see, that's why. I guess that's not the same problem then because there is no warning in his log as mine (i.e time="2024-03-08T15:31:30+01:00" level=warning msg="Using local development path to serve static files"
). I actually have an empty static folder.
However, it seems that activating verbosity (--verbose
) as he did doesn't produce the log to endpoints calls from GIN
@undera Can you confirm this problem ? Or maybe they are written on a file somewhere else?
@deiga Can you try to execute just helm dashboard
and see if in the log you get the call to endpoints (e.g GET "/" 404)? If still nothing gets reflected, maybe it is really something like a proxy/service intercepting the request.
Description
I've just installed the plugin and wanted to try it out. But when I run
helm dashboard
I get a 404 page.I've checked that
kubectl config current-context
has a correct context set and I've tried to start dashboard withhelm --kube-context foo dashboard
, but to no avail.$ helm dashboard --verbose
$ kubectl version
$ helm version
Screenshots
No response
Additional information
No response