Remote Console not accessing the VMs

[RodPin]

Hello!

I'm facing a quite strange issue as the Remote Session console cannot reach any of the VMs.

Initially, I thought that some policy implemented in the PC I'm using to access would be blocking it after hardening it, although, even after testing with another clean PC, I stil lcannot make the connection.

I think it's strange because I still can RDP to the Windows machines and also SSH into the Morpheus VM. I also can still Remote Console to the host computer.

This is the log when trying to connect to Morpheus VM.

==> /var/log/morpheus/guacd/current <==
2025-09-26_00:25:50.24630 guacd[23313]: INFO: Creating new client for protocol "vnc"
2025-09-26_00:25:50.24682 guacd[23313]: INFO: Connection ID is "$c19bf196-a88b-4471-8c15-e05c8e0644bb"
2025-09-26_00:25:50.25087 guacd[30330]: INFO: Cursor rendering: local
2025-09-26_00:25:50.25127 guacd[30330]: INFO: User "@c1b9fcca-fe27-40a0-9654-29d1fff91472" joined connection "$c19bf196-a88b-4471-8c15-e05c8e0644bb" (1 users now present)
2025-09-26_00:25:50.25154 guacd[30330]: ERROR: Unable to connect to VNC server.
2025-09-26_00:25:50.25356 guacd[30330]: INFO: User "@c1b9fcca-fe27-40a0-9654-29d1fff91472" disconnected (0 users remain)
2025-09-26_00:25:50.25366 guacd[30330]: INFO: Last user of connection "$c19bf196-a88b-4471-8c15-e05c8e0644bb" disconnected
2025-09-26_00:25:50.50462 guacd[23313]: INFO: Connection "$c19bf196-a88b-4471-8c15-e05c8e0644bb" removed.

Another thing that I've noticed is that if I try to clone a VM, I get an error due to low Cluster resources. I don't understand, as the Cluster has plenty of resources available.

Even if I try to Provison a VM with very low consuming resources, for example (1 CPU 512MB) Morpheus still will give me an error bur will create a instance with error.

I thanks in adance for any help provided.

[RodPin]

Adding some screenshots..

Cluster resources:

Cluster resources

Remote console window:

Remote Terminal windows

[RodPin]

I stil cannot connect to the Console, but at least found a workaround for the Cloning, so, please, don't close the post yet...

Basically, I did the clonning manually using virsh:

virt-clone --original=<source_vm_name> --name=<new_vm_name> --auto-clone

Then, I manually started the VM:

virsh start VM_NAME

Since I still could access the VMs using Windows RDP, I accessed the clone and adjusted the IPs as per my network configuration. Luckly, my VM had 2 interface cards configured, so I configured one first in the same network as another VM, and then from this other VM, RDP again and modified my RDP Network NIC IP.

Then, had to wait for the VM to show in the Cloud as "Unmanaged":

From Google Gemini:
- VM Discovery:
   Once the KVM host is successfully onboarded and the cloud is configured to "Inventory Existing Instances," Morpheus will automatically discover the VMs running on that KVM host during its regular cloud syncs (typically every five minutes by default).
   These discovered VMs will appear on the VMs tab of the Cloud detail page and also on the central Infrastructure > Compute > Virtual Machines list page. 

After that, just follow Morpheus instructions to allow it to manage the VM.