# In case of Lens Spaces/Cluster Connect issues

**URL:** <https://forums.k8slens.dev/t/in-case-of-lens-spaces-cluster-connect-issues/2346>\
**Category:** Tips and Tricks\
**Tags:** lens-desktop, kubernetes\
**Created:** [November 30, 2023, 2:25pm UTC](https://forums.k8slens.dev/t/in-case-of-lens-spaces-cluster-connect-issues/2346 "2023-11-30T14:25:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![emeste](https://forums.k8slens.dev/user_avatar/forums.k8slens.dev/emeste/32/302_2.png) [@emeste](https://forums.k8slens.dev/u/emeste)\
**Post date:** [November 30, 2023, 2:25pm UTC](https://forums.k8slens.dev/t/in-case-of-lens-spaces-cluster-connect-issues/2346/1 "2023-11-30T14:25:22Z")

</div>

If you’re experiencing Lens Spaces or Cluster Connect issues, you may have to restart your `bored-agent` pod, which can be found in the `lens-platform` namespace.

By restarting the pod in the affected clusters, your issue should be resolved.  
Don’t hesitate to contact us if you still have difficulties accessing Lens Spaces or Cluster Connect.

You can find more information here:

[https://docs.k8slens.dev/lens-teamwork/cluster-connect/](https://docs.k8slens.dev/lens-teamwork/cluster-connect/)