/
"Session expired" message displayed in control center

"Session expired" message displayed in control center

 Problem

Not able to access control center and always getting “session expired” message on UI.

 Solution

A session expired message is observed when session stickiness is not configured.
1. In case you are using Load Balancer, check if you have enabled the sticky session feature for it? Please check here for more details.

2. In the case you are using HiveMQ Operator, the following config is also required to be configured in your values.yaml. In addition, if you are using a load balancer then please enable the sticky session feature for it as well.

- name: "cc" port: 8080 expose: true patch: - '[{"op":"add","path":"/spec/sessionAffinity","value":"ClientIP"}]'
  1. If you have created a service to expose the control center port, please add the following line to your service spec: sessionAffinity: "ClientIP". You can refer to the example below for guidance:

kind: Service apiVersion: v1 metadata: name: hivemq-service labels: app: hivemq hivemq-cluster: hivemq-cluster1 spec: sessionAffinity: "ClientIP" selector: hivemq-cluster: hivemq-cluster1 ports: - name: cc protocol: TCP port: 8080 targetPort: 8080 type: LoadBalancer

 Related articles

Related content

Expose the HiveMQ Control Center and Rest API using Ingress
Expose the HiveMQ Control Center and Rest API using Ingress
Read with this
Expose HiveMQ Control Center service using HiveMQ Operator
Expose HiveMQ Control Center service using HiveMQ Operator
More like this
ERROR - HiveMQ Enterprise Security Extension: Unhandled exception in Rest API authentication java.lang.IllegalStateException: No authorization-key set
ERROR - HiveMQ Enterprise Security Extension: Unhandled exception in Rest API authentication java.lang.IllegalStateException: No authorization-key set
More like this
HiveMQ Kubernetes Operator repeatedly shutdown/restarts pods every 2 hours
HiveMQ Kubernetes Operator repeatedly shutdown/restarts pods every 2 hours
More like this