VM client socket is closed

K

KevDog

Patron
Joined
Nov 26, 2016
Messages
462
Sometimes I hate the Truenas GUI abstraction layer, particularly when there just seems to be a python problem. Currently running True Nas Core 13 U5.3.

I have 8 VMs listed within the TrueNAS Core GUI and I'm aware via SSH I can connect to 7 of the 8 VMs through CLI SSH. The GUI however can't seen to control any VM. Is there a work around?

Here are some screenshots:
 

Attachments

  • Screenshot 2023-11-19 at 1.46.13 PM.png
    Screenshot 2023-11-19 at 1.46.13 PM.png
    815.9 KB · Views: 47
  • Screenshot 2023-11-19 at 1.47.20 PM.png
    Screenshot 2023-11-19 at 1.47.20 PM.png
    566 KB · Views: 49
  • Screenshot 2023-11-19 at 1.51.28 PM.png
    Screenshot 2023-11-19 at 1.51.28 PM.png
    961.3 KB · Views: 37
You must log in or register to reply here.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "VM client socket is closed"

Similar threads

sepahewe
"libvirt.libvirtError: internal error: client socket is closed" when trying to start a VM
2
Replies
27
Views
11K
Tuxxin
Tuxxin
OldTeaGuyy
WOL VM on TrueNAS-Scale
Replies
6
Views
1K
jgreco
jgreco
R
VM VNC doesn't allow inputs after random amount of uptime
Replies
1
Views
1K
Frank_S
F
apwiggins
[RESOLVED] TrueNAS GUI inaccessible, middlewared socket connect error
Replies
8
Views
6K
pschatz100
P
S
Slow replication via SSH. High CPU usage despite AES-ni
Replies
11
Views
2K
s851
S
Top