

A cluster that doesn't answer, and what to try.
Connecting to a cluster
Unreachable: Can't reach the cluster
Unreachable: Can't reach the cluster
- Check that the cluster is running, and that this computer can reach it. Many clusters are only reachable over a VPN or a tunnel.
- If you have
kubectl,kubectl --context <name> get --raw /versiontells you whether the API server answers from this computer. - Behind a company’s proxy, Lumovi goes through the one your shell uses (
HTTPS_PROXY), or your kubeconfig’sproxy-url. The proxy needs credentials (407) wants them in the proxy’s URL (http://user:password@proxy:3128), and The proxy didn’t open a tunnel (it answered 403) means it refused the address. A cluster on your own network may need to be inNO_PROXY. See Proxies and certificates. - Choose Try again, or Reload on the start screen, once the network is back.
Timed out: The cluster isn't responding
Timed out: The cluster isn't responding
LUMOVI_REQUEST_TIMEOUT_MS. On macOS, quit Lumovi, then:Certificate error: The cluster's certificate couldn't be verified
Certificate error: The cluster's certificate couldn't be verified
- Its certificate isn’t signed by a certificate authority Lumovi trusts: the certificate authority in your kubeconfig doesn’t match the API server’s certificate. This happens when a cluster is recreated or its certificates rotate. Get a fresh kubeconfig entry from wherever the cluster came from, for example
aws eks update-kubeconfig,gcloud container clusters get-credentialsoraz aks get-credentials, then choose Reload. Behind a proxy that inspects HTTPS, the proxy signs it with its own: ask for the cluster to be left uninspected, or put the proxy’s authority in your kubeconfig. - Its certificate has expired: the cluster’s, or the proxy’s.
- Its certificate is for another name: the address in your kubeconfig isn’t one the certificate names.
tls-server-nameon the cluster can name the one it does. - TLS handshake failed, and why, for anything else.
Plain HTTP blocked: Plain HTTP isn't allowed
Plain HTTP blocked: Plain HTTP isn't allowed
http://, for example through kubectl proxy. Lumovi only uses unencrypted connections when the kubeconfig says so for that cluster, the same rule as the official JavaScript client:Credentials failed: Couldn't get credentials
Credentials failed: Couldn't get credentials
gke-gcloud-auth-plugin, aws eks get-token or kubelogin, and the plugin failed.- The credential plugin “…” wasn’t found. Install the plugin, or make sure it’s on your
PATH. On macOS and Linux, Lumovi readsPATHfrom your login shell when it starts, even when you open it from the Dock or a launcher. So the plugin must be on thePATHyour shell profile sets up. Restart Lumovi after changing it. - Could not get credentials: … The plugin ran but failed, most often because you’re signed out of your cloud provider. Sign in again (
gcloud auth login,aws sso login,az login…), then choose Try again.
Forbidden: Access denied
Forbidden: Access denied
Your kubeconfig couldn't be read, or no clusters yet
Your kubeconfig couldn't be read, or no clusters yet
- Your kubeconfig couldn’t be read. A file has a syntax error. Lumovi names the file and the first line of the problem. Fix the file, then choose Reload, or Choose a kubeconfig… to read another. When other files can be read, they still load, and a notice above the list names the one that couldn’t.
- No clusters yet. Lumovi found no contexts. Choose a kubeconfig… reads the file you use with kubectl, and Add a cluster takes one you paste. See Connect your clusters.
- The kubeconfig you chose is gone. A file you chose in Lumovi was moved or deleted. Choose it again where it is now, or go Back to KUBECONFIG and ~/.kube/config.
Clusters are missing, though kubectl sees them
Clusters are missing, though kubectl sees them
kubectl in your terminal uses the KUBECONFIG your shell profile exports. Lumovi opened from the Dock, Spotlight or a launcher doesn’t see that variable (it takes only PATH and the proxy from your shell), so it reads ~/.kube/config. The kubeconfig files button, at the bottom of the start screen, shows which files it read.Choose your files in Lumovi, which keeps them, start Lumovi from your terminal, or set KUBECONFIG where apps see it. See Setting environment variables.While you work
A list stops at 5,000 objects
A list stops at 5,000 objects
LUMOVI_MAX_LIST_ITEMS.On the Workloads page and plugin pages, the note says Some lists are too long to load whole, and a kind that can’t be listed at all says Couldn’t list … above the rest.An action is grayed out
An action is grayed out
- Your account can’t … in …. Your RBAC doesn’t allow it. See Permissions.
- Changes are turned off for this cluster. You,
LUMOVI_READ_ONLY, or your organization’s policy made it read-only. On a server, it’s read-only for everyone, and says who made it so: “Changes are turned off for this cluster: jane@example.com made it read-only for everyone.” Ask them, or Lumovi’s admins. See Read-only mode.
Lumovi started without something it was given
Lumovi started without something it was given
- Your organization’s policy, which then locks the most it could: see below.
- A certificate authority’s file the policy names: The certificate authorities in … can’t be read: …. Lumovi trusts the others, and the system’s.
- A proxy that isn’t a URL, in
HTTPS_PROXYorHTTP_PROXY:HTTPS_PROXY isn’t a proxy’s URL: give it as http://host:port (or https://).Lumovi connects without it. Check your shell’s profile, or the environment variable.
Only Lumovi's admins change it
Only Lumovi's admins change it
Every cluster is read-only, and AI assistants are off
Every cluster is read-only, and AI assistants are off
KUBECONFIG, or ~/.kube/config. As it starts, a notice says so, titled “Lumovi started without something it was given”, and the Read-only badge next to an object’s actions says why: “Lumovi can’t use your organization’s policy (…), so it changes no cluster until it’s put right.” Send that to your IT: the policy isn’t an administrator’s alone, isn’t JSON, has a key Lumovi doesn’t know, or, on Windows, couldn’t be read from the registry (where people may run neither reg.exe nor PowerShell, let them run reg.exe). See When it can’t be used.It changed in the meantime
It changed in the meantime
A shell says the container has no shell
A shell says the container has no shell
A shell on a node doesn't start
A shell on a node doesn't start
- … doesn’t allow privileged pods: its Pod Security level is stricter than privileged. Choose Settings in the node’s Shell tab, and a namespace that allows privileged pods, like
kube-system. - … couldn’t start … (ErrImagePull): …. The node can’t pull the image. Choose one it can pull in Settings, like a copy in your own registry.
- … didn’t start the node shell’s pod in … seconds. The node’s kubelet may not be running, or the image takes long to pull.
- … has no shell of its own. Talos and Bottlerocket nodes have none. Choose Shell in the pod.
- … has no nsenter. A shell on the node itself needs the image’s
nsenter. Choose an image that has it, likealpine, in Settings, or a shell in the pod. - No node shell access. Your account can’t create pods, read them, or open shells in them, in the node shells’ namespace. Ask for them, or choose another namespace in Settings (on a server, Lumovi’s admins do, for everyone).
- Node shells need a Linux node. Windows nodes can’t have one.
- Node shells are off. The Lumovi server you use turned them off.
A terminal won't start, or kubectl points elsewhere
A terminal won't start, or kubectl points elsewhere
SHELL names a shell that isn’t on your computer. Set it to one that is, and start Lumovi again. Without SHELL, terminals start zsh on macOS and bash on Linux. On Windows, they start Windows PowerShell.PowerShell is still starting. On Windows, a terminal says so when PowerShell has drawn nothing for 5 seconds; the line goes once it draws. Two things usually hold it up. Your profile: Measure-Command { . $PROFILE }, in PowerShell, says how long it takes, and moving slow work out of it helps every terminal. A virus scanner that checks PowerShell as it starts: your IT can tell you whether it does, and whether that can be eased.kubectl uses another cluster. Your shell’s startup files probably set KUBECONFIG, which replaces the terminal’s own. Have them add to it instead, so the terminal’s file stays first. See Terminals.A terminal says it uses the kubectl on your PATH
A terminal says it uses the kubectl on your PATH
- Lumovi couldn’t ask the cluster its version (it didn’t answer within 3 seconds). The cluster isn’t reachable now, and Lumovi has never learned its version: connect its VPN, say, and open another terminal.
- the cluster says it’s Kubernetes 1.13, and Lumovi gets kubectl for 1.25 or later. Lumovi gets no kubectl older than 1.25. Use a kubectl of your own that suits that cluster.
-
Lumovi gets kubectl only over HTTPS, and … isn’t (LUMOVI_KUBECTL_MIRROR).
LUMOVI_KUBECTL_MIRRORnames a mirror over plainhttp, or isn’t a URL. Give anhttpsone, or unset it. - kubectl v1.34.9 is still downloading, for the terminals opened once it’s done. Open another terminal once it’s done.
- dl.k8s.io didn’t answer within 10 seconds, or Lumovi couldn’t get kubectl 1.34 to match the cluster (…): dl.k8s.io can’t be reached from this computer, and Lumovi kept none of that version. Behind a company’s proxy, see Proxies and certificates. Lumovi tries again 10 minutes later. Your organization can name a mirror in its policy.
- Lumovi couldn’t get kubectl 1.34 to match the cluster (dl.k8s.io’s kubectl v1.34.9 couldn’t be verified as Kubernetes’ own, and may have been changed: …), or (… published no signature for kubectl v1.34.9): the download isn’t signed by Kubernetes’ release, or its signature doesn’t hold, so it isn’t used. A proxy that changes what it passes on can do that. If it’s a mirror’s, check what it keeps. See A kubectl that matches the cluster.
- (… couldn’t be verified as Kubernetes’ own, so it may have been changed, or Kubernetes has changed how it signs and Lumovi needs an update: …), or the same with Sigstore has changed its certificate authority or Sigstore has changed its logs: it’s signed, but not as this Lumovi knows Kubernetes signs, or not under Sigstore’s authority and logs as it knows them. If Kubernetes or Sigstore has changed them, every kubectl signed since is refused until you update Lumovi, once a release knows the new ones; meanwhile, terminals use yours, or the newest one kept. If neither has, it may have been changed, as above.
-
(artifacts.corp.example.com published no signature for kubectl v1.34.9, and your organization’s policy requires one): your organization’s policy requires Kubernetes’ signature from its mirror, and the mirror keeps none for that kubectl. Whoever runs the mirror can add Kubernetes’
.sigand.certbeside it.
A port can't be forwarded
A port can't be forwarded
The map shows a card as Not found
The map shows a card as Not found
Something went wrong
Something went wrong
This page doesn't exist
This page doesn't exist
Usage and metrics
No live CPU or memory
No live CPU or memory
kubectl top. Without it, the overview says Live usage needs metrics-server, and Lumovi shows requests and limits against capacity instead. Install metrics-server in the cluster to see live usage. See Live usage.No usage history
No usage history
- No Prometheus found. None of the cluster’s services looks like Prometheus or VictoriaMetrics. If yours runs under another name, choose Choose a service to pick its namespace, service, port and path (
/select/0/prometheusfor vmselect). Look again searches again, after you install one, say. - Can’t read usage history. There’s a source, or something that looked like one, but reading it failed. The message under it says why:
- Your account can’t list services, so Lumovi can’t look for Prometheus. Choose its service yourself, or ask for
liston services. - Your account can’t reach … through the API server (it needs get on services/proxy). Lumovi reaches the source through the API server with your credentials, so you need
getonservices/proxyin its namespace. - … didn’t answer PromQL or It answered, but not like Prometheus. The service, port or path isn’t a PromQL endpoint. Choose the right one.
- Your account can’t list services, so Lumovi can’t look for Prometheus. Choose its service yourself, or ask for
- Usage history is off. It was turned off for this cluster. Choose Change to turn it back on.
Right-sizing has no recommendation
Right-sizing has no recommendation
- Too new: it has less than a day of history. Recommendations need a day, and grow more confident up to a week.
- No usage: Prometheus has no CPU and memory samples for its containers in the last week, or it had no pods.
- Autoscaled: a VerticalPodAutoscaler sets its requests, so Lumovi leaves it to it.
Helm
Lumovi couldn't run helm
Lumovi couldn't run helm
LUMOVI_HELM names a helm that isn’t there, or can’t run, or when you run it from source (npm run dev) without helm on your login shell’s PATH. Set LUMOVI_HELM to a helm that runs, or unset it to use the one Lumovi ships with.Helm couldn't do it
Helm couldn't do it
helm said. A failed upgrade is often a chart or values problem, which the dry run usually catches first.If the release is managed by Flux, Lumovi says so and links to its HelmRelease. Flux puts back changes made any other way, so make the change in Flux instead.Couldn't reach a chart repository or Artifact Hub
Couldn't reach a chart repository or Artifact Hub
- The proxy needs credentials (407): give them in its URL, as
http://user:password@host:port. - The proxy didn’t open a tunnel (it answered 403).: the proxy doesn’t allow the address.
- Its certificate isn’t signed by a certificate authority Lumovi trusts (…): a proxy that inspects HTTPS signs with an authority your computer doesn’t trust yet. IT installs it in your system’s certificates, or names it in your organization’s policy. On a server, give it with
extraCA.
AI assistants
Lumovi can't use its port
Lumovi can't use its port
An assistant can't connect, or is turned away
An assistant can't connect, or is turned away
- Lumovi needs its token: set this assistant up again from Lumovi. It sent no token, or an old one, after New token…, say. Claude Desktop is told something else: see Claude Desktop doesn’t use Lumovi, below. Set it up again from the AI assistants page. See Connect an assistant.
- That session has ended: start a new one. Lumovi was restarted, turned off and on, or let the assistant go after six hours without a word from it. Most assistants start a new session by themselves. If yours doesn’t, reconnect it, or restart it.
- Web pages may not connect to Lumovi. The request came with an
Originheader, as a browser’s requests do. Tools that run in a browser can’t connect. - Only this computer may connect. The request was addressed to a name other than
127.0.0.1orlocalhost. Use the address the dialog shows. - That’s more than Lumovi takes: 4 MB at most. A message, like a manifest to apply, was larger than that.
Claude Desktop doesn't use Lumovi
Claude Desktop doesn't use Lumovi
- Claude Desktop isn’t installed on this computer. Lumovi found no folder of Claude Desktop’s settings. Install it, open it once, and try again.
- Claude Desktop’s settings (…) aren’t valid JSON, so Lumovi left them alone. Fix the file it names, and choose Add to Claude Desktop again.
- AI assistants are turned off in Lumovi: open Lumovi, and turn them on in its AI assistants settings.
- Lumovi didn’t start: open it, and check that AI assistants are on. Lumovi wasn’t running, and didn’t listen within 30 seconds of being started. Open it yourself.
- Lumovi isn’t answering: open it, and try again.
- What listens on Lumovi’s port (47830) can’t show it’s Lumovi, so Lumovi’s token isn’t sent to it: open Lumovi, and set this assistant up again. Another program listens on Lumovi’s port while Lumovi isn’t running, or the token in Lumovi’s settings isn’t the one Lumovi uses. Lumovi’s token isn’t sent there, and Lumovi isn’t started over it. Open Lumovi, and if it can’t use its port, choose another; then choose Add to Claude Desktop again.
- Lumovi isn’t running: open it, and try again. Lumovi isn’t open, and can’t be started for Claude Desktop yet: Lumovi notes how to start it each time you open it. Open it yourself.
- Lumovi’s settings name no port it listens on: open Lumovi, and choose AI assistants’ port again. The port in Lumovi’s settings isn’t one Lumovi could listen on, so Claude Desktop’s messages, and the token with them, aren’t sent anywhere. Choose the port again on the AI assistants page.
A change an assistant asked for wasn't made
A change an assistant asked for wasn't made
- … wouldn’t work: …. The cluster refused the dry run: your account can’t make the change, the cluster is read-only, or the object isn’t valid. The rest of the message is the cluster’s.
- Lumovi doesn’t let AI assistants change …: the person’s AI permissions say so (…). Your permissions say Never there, by the rule named, or the defaults. Check a namespace, on the Permissions tab, says which. When it says “this server’s administrator says so”, it’s a limit only they can change.
- Lumovi doesn’t show AI assistants the Secrets in … or Lumovi doesn’t let AI assistants read logs in …: the same, for Secrets and logs. See What assistants see.
- Not approved in time. Nobody answered within five minutes.
- … withdrew a change. The assistant gave up on a call that was waiting for the change: it was stopped, or it ended its session, or you turned assistants off. On a server, also when you disconnected it, or your session ended. Ask it again.
- … wasn’t made: … changed after it was shown (…). You approved it, but it would no longer do what the diff showed: the object changed meanwhile, or, for a deletion, it’s another object under the same name. Lumovi tells the assistant to ask again, so you see it as it is now.
- … failed: …. You approved it, but the cluster refused it then: the object is gone, say. The rest of the message is the cluster’s.
wait_for_change to hear how it went. That says No change with id … is waiting when the change was answered a while ago, or never asked for.See Approving changes.An assistant can't sign in to your team's Lumovi
An assistant can't sign in to your team's Lumovi
- It doesn’t say which assistant it is. or It goes back somewhere the assistant didn’t name. The request didn’t come from the assistant as it registered. Start again from the assistant.
- It’s for …, not Lumovi’s …. The assistant was set up with another address. Set it up again with the one the AI assistants page shows.
- Allow assistants from Lumovi’s own page. Lumovi doesn’t recognize the address the page was opened at as its own: the administrator should set
url. - This server’s administrator has turned AI assistants off. So does the AI assistants page.
An assistant says Lumovi restarted
An assistant says Lumovi restarted
Lumovi restarted since alice@example.com last used it: open Lumovi in your browser, and Claude Code picks up where it left off. You sign in with a token, or your team’s single sign-on passes your own token on, and Lumovi keeps it sealed with a key only your browser has. Open Lumovi, and the assistant carries on. See When Lumovi restarts.The audit log
I see only my own events
I see only my own events
Check integrity says the log doesn't hold
Check integrity says the log doesn't hold
Lumovi looked through the most recent events
Lumovi looked through the most recent events
An export has fewer events than I expected
An export has fewer events than I expected
Audit events couldn't be kept or sent
Audit events couldn't be kept or sent
Installing
Windows says it protected your PC
Windows says it protected your PC
The AppImage doesn't start
The AppImage doesn't start
chmod +x Lumovi-*.AppImage. Then run it from a terminal to see any error it prints.In your cluster
Pages keep reconnecting
Pages keep reconnecting
LUMOVI_HEARTBEAT_SECONDS). Keep that shorter than the idle timeouts of the proxies in between. See Address and ingress.The pod doesn't start: CreateContainerConfigError
The pod doesn't start: CreateContainerConfigError
proxy.secret, the pod needs that Secret, in Lumovi’s namespace, with the key HTTPS_PROXY. Without either, Kubernetes doesn’t start the container, and kubectl describe pod says which is missing. Create it, or fix its key’s name: see Proxies and certificate authorities.Lumovi stops: HTTPS_PROXY isn't a proxy's URL
Lumovi stops: HTTPS_PROXY isn't a proxy's URL
HTTPS_PROXY or HTTP_PROXY, which the chart sets from proxy, can’t be read as a URL: HTTPS_PROXY isn’t a proxy’s URL: give it as http://host:port (or https://). Lumovi doesn’t say what it was, as it can hold credentials. Check it, and encode characters like @ in a password as %40. See Proxies and certificate authorities.The chart refuses more than one replica
The chart refuses more than one replica
More than one replica (replicaCount) needs auth.keepSessions: without it, each replica keeps who's signed in, and what's set for everyone (the clusters made read-only, say), in its own memory, and they don't agree. Leave auth.keepSessions on, or run one replica. More than one also needs assistants.enabled: false, audit.persistence.enabled: false, and sticky sessions. See replicaCount.A cluster says it was changed outside Lumovi
A cluster says it was changed outside Lumovi
<release>-state, or state.json), by whoever can write there, not through Lumovi. Lumovi kept the stricter: read-only if either copy was, and its metrics source and node shells as it last set them. The banner says what it did: “production’s read-only was turned off outside Lumovi, and Lumovi made it read-only again.”, “production was made read-only outside Lumovi.”, or “What’s set for production was changed outside Lumovi, and Lumovi put it back.” The audit log has it, by Lumovi itself, with outside: true.- Choose Keep it read-only or Allow changes (Keep it changeable or Make it read-only, where it’s changeable). Either is your own change, recorded as yours, and the banner goes.
- Find who could write there: whoever may
patchthat Secret, or write the file, and controllers that sync Secrets into Lumovi’s namespace, or put a backup back.
Signing in or the webhook fails on a certificate
Signing in or the webhook fails on a certificate
extraCA, or leave the address out of the proxy with proxy.noProxy. Its certificate has expired and Its certificate is for another name are said the same way. See Proxies and certificate authorities.Lumovi's pod is Pending
Lumovi's pod is Pending
audit.persistence.storageClass, or audit.persistence.enabled: false. See Where it’s kept.Another Lumovi keeps its audit history there
Another Lumovi keeps its audit history there
Not for you, here
Not for you, here
Lumovi stops at start with an access setting
Lumovi stops at start with an access setting
LUMOVI_ACCESS (the chart’s access.policy), or what admins set and Lumovi kept, doesn’t make sense, and the log says where: LUMOVI_ACCESS: grants[0].who[0] names a group there isn’t: “nobody”. Lumovi stops rather than let anyone do more. See Access for your team.Everyone was signed out
Everyone was signed out
auth.keepSessions: false, or without the chart, neitherLUMOVI_STATE_SECRETnorLUMOVI_DATA_DIR. The log says, as Lumovi starts:Who’s signed in, the AI assistants they allowed, and people’s pins and saved views are kept in memory: they’re lost when Lumovi stops., then, in a cluster,The Helm chart’s auth.keepSessions keeps them (LUMOVI_STATE_SECRET)., andRun a single replica so: …- The key changed, or was lost:
12 of what Lumovi kept doesn’t open with its key (it changed, they were, or another replica uses another): left as they are, unused, until they’ve been so for 15 minutes, then let go.With Argo CD, or anything else that renders the chart withhelm template, each render makes a new key: give your own, inauth.stateKeySecret. See Sessions across restarts. - Writing it failed, before the restart:
Lumovi can’t keep who’s signed in (…): if it restarts now, what changed since is lost., thenLumovi keeps who’s signed in again.once it can. - It didn’t all fit in a megabyte:
What Lumovi keeps would be more than the 1000 kB it may hold: the 40 sessions that end soonest aren’t kept (they sign in again after a restart). - What’s kept can’t be read, edited by hand, say:
What Secret lumovi/lumovi-state kept can’t be read (…): everyone signs in again., with why in the brackets - Lumovi was uninstalled, which deletes the Secret and its key.
- More than one replica, without sticky sessions: each knows the sessions started on it.
Lumovi doesn't start: its sessions' Secret or key
Lumovi doesn't start: its sessions' Secret or key
Lumovi can’t read Secret lumovi/lumovi-state, where it keeps who’s signed in, the AI assistants they allowed, and people’s pins and saved views: …. The Secret isn’t there, or Lumovi may notgetit: withrbac.create: false, give its service accountgetandpatchon<release>-state.LUMOVI_STATE_SECRET needs LUMOVI_STATE_KEY: the key what’s kept is sealed with, from a Secret of its own (the chart makes one).Without the chart, set both.LUMOVI_STATE_KEY must be at least 32 characters, random ones.The key inauth.stateKeySecret’s Secret is too short: make one withopenssl rand -base64 48.
key, isn’t there (CreateContainerConfigError). See LUMOVI_STATE_SECRET.The cluster doesn't accept this token
The cluster doesn't accept this token
kubectl create token NAME --namespace NAMESPACE. Lumovi asks the cluster who a token belongs to with a SelfSubjectReview, which needs Kubernetes 1.28 or later. See Tokens.Your session ended
Your session ended
A fleet doesn't start
A fleet doesn't start
- A fleet needs single sign-on or a proxy (LUMOVI_AUTH=oidc or proxy): a pasted token only says who someone is to one cluster.
- LUMOVI_FLEET_SECRETS reads Secrets of the cluster Lumovi runs in, and it isn’t running in one, or LUMOVI_FLEET_LOCAL is true, but Lumovi isn’t running in a cluster: outside Kubernetes, use a kubeconfig or agents instead.
- LUMOVI_FLEET_KUBECONFIG isn’t a kubeconfig: …
- LUMOVI_FLEET_AGENTS[0] (private-eu) needs a token of at least 32 characters, or its tokenSha256.
An agent doesn't connect
An agent doesn't connect
-
The hub at … refused this agent: it doesn’t know this name and token. Lumovi’s log says An agent was refused, with the name. The token’s SHA-256 was taken with a trailing newline, the agent’s name (
clusterName,in-clusterunless you set it) isn’t the one Lumovi lists, Lumovi wasn’t restarted after its list of agents changed, or a proxy in front of Lumovi answersapi/agentitself. - … refused this agent: another agent connected as it (do two clusters use the same name and token?). Give each agent its own name and token.
-
Can’t reach the hub at …, then Connecting again in … s: the agent can’t reach Lumovi’s address. It keeps trying. Behind a proxy, give it
proxyin the chart: The proxy … needs credentials to … (407) wants them in its URL, and … didn’t open a tunnel to … refused the address. See Proxies and certificate authorities. - Nothing from the hub in 61 s: something between them, often a proxy’s idle timeout, drops a quiet connection. Lumovi pings every 30 seconds by default, so let idle connections live longer than that.
-
LUMOVI_HUB_URL must be https, not http://…: the agent’s token and its cluster’s would cross the network as they are. The agent stops: give Lumovi’s
httpsaddress.httpreaches only a Lumovi on the same machine (localhost,127.0.0.1or[::1]). The chart refusesagent.hubUrloverhttpthe same way, but on the same machine.
An agent's cluster says Agent not trusted
An agent's cluster says Agent not trusted
agent.refused.- Its cluster’s certificate authority changed, rotated or rebuilt: an admin (or anyone, where Lumovi has none) trusts the new one with Trust it… on the page of every cluster, pasting its SHA-256 from the cluster itself:
kubectl get configmap kube-root-ca.crt -n default -o jsonpath='{.data.ca\.crt}' | openssl x509 -noout -fingerprint -sha256, run with your own access to that cluster, not through Lumovi. Lumovi trusts it only if the agent sends that one. Where Lumovi has no admins, anyone signed in can. Or set itscaSha256inLUMOVI_FLEET_AGENTS, and restart Lumovi. - It didn’t change: someone else has the agent’s token, and connected with it. Don’t trust it. Make a new token, and give its SHA-256 to Lumovi.
- The card says Certificate error, with “other than the one LUMOVI_FLEET_AGENTS names for it”: its
caSha256is set, and isn’t this one. Change it there, and restart Lumovi.
A cluster I added doesn't appear
A cluster I added doesn't appear
A cluster is missing from the fleet
A cluster is missing from the fleet
A cluster in a fleet can't be used
A cluster in a fleet can't be used
Reporting a problem
If none of this helps, please open an issue. In the desktop app, Help → Report an Issue… opens the same page. It helps to include:- your Lumovi version, shown at the bottom of the sidebar,
- your operating system, and how the cluster is run (EKS, GKE, kind…),
- what you did, what you expected, and what happened instead,
- the details from the error screen, which Copy details copies.