Server not found

[d3xma]

Hey everybody,

is just installed the chart on my cluster, but accessing the dashboard results in an infinite search for the server.
It seems that the server running in the cluster cant be found.

Do you have any solution or idea whats causes this problem?

BR

[Zageron]

This has happened to me as well.
Installed helm install plex ./charts/kube-plex --namespace plex --set claimToken=myclaimtoken --set service.type=LoadBalancer

❯ kubectl get service
NAME             TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                                      AGE
plex-kube-plex   LoadBalancer   10.152.183.60   192.168.1.120   32400:32175/TCP,80:32402/TCP,443:30307/TCP   17m

Opens the page just fine, logs me in to my account, shows my existing server running. If I disable my existing server, I don't see a new server that should be here.

Any ideas?

Edit: More details

❯ microk8s status
microk8s is running
high-availability: no
  datastore master nodes: 192.168.1.213:19001
  datastore standby nodes: none
addons:
  enabled:
    dashboard            # The Kubernetes dashboard
    dns                  # CoreDNS
    ha-cluster           # Configure high availability on the current node
    helm3                # Helm 3 - Kubernetes package manager
    ingress              # Ingress controller for external access
    metallb              # Loadbalancer for your Kubernetes cluster
    metrics-server       # K8s Metrics Server for API access to service metrics
    storage              # Storage class; allocates storage from host directory

[lethek]

I've been struggling with seemingly the same issue for the last couple hours. However, I've been using an Ingress rather than a LoadBalancer service. The ingress acted exactly the same as @Zageron described - I was able to log in, but the web-UI only showed my pre-existing Plex servers from elsewhere which were linked to my account.

What finally worked for me just now was (despite the new ingress) I had to use kubectl port-forward to the pod's 32400 port then open in my browser the /web path on the locally mapped port.

E.g.
kubectl port-forward deployment/plex 57085:32400

Then open in my browser: http://127.0.0.1:57085/web

For some reason, it was important for me to manually add /web onto the URL. If I left it off then I ended up getting an XML document that looked like some kind API response. I'd tried port forwarding many times earlier, seen the XML, felt confused and not thought of trying /web.

[tibbe]

I had the same issue and @lethek 's answer above worked for me.