TUNNEL_ERROR while trying to access VM via VNC

Hi guys…

I already check this link, but it doesn’t has an answer :frowning:

Scenario:

  • Ubuntu 20.04 (10.1.3.200) wich will act as an hypervisor for OpenNebula, wich is:
  • An LXC container as a front-end (for, obviuosly, OpenNebula ) running Ubunut 20.04 (10.1.3.254)
    I run the installation without any major problem but I have encounter a problem when I try to access a VM via VNC, the VM start ok (I can even ping it from both the front-end and the hypervisor) and the logs (/var/log/one/[VM_ID.log]) shows no error related to the VMs. But when I try to access via VNC to the VM the new created tab shows me the TUNNEL_ERROR.

Versions of the related components and OS (frontend, hypervisors, VMs):
Hypervisor: Ubuntu 20.04, KVM
Front-End: Ubuntu 20.04, with OpenNebula 6.2.0-1.ce

Steps to reproduce:
Normal installation

Current results:
When try to access a VM via VNS it shows the error: TUNNEL_ERROR

Expected results:
Access to the VM console/graphic interface via the web VNC


EXTRA:
The only error I’m capable of see is located in /var/log/one/oned.log when launching the web VNC:

Thu Nov 11 17:49:19 2021 [Z0][ReM][D]: Req:8000 UID:0 IP:127.0.0.1 one.vm.info invoked , 2, false
Thu Nov 11 17:49:20 2021 [Z0][ReM][D]: Req:8000 UID:0 one.vm.info result SUCCESS, "<VM><ID>2</ID><UID>0..."
Thu Nov 11 17:49:21 2021 [Z0][ReM][D]: Req:3472 UID:0 IP:127.0.0.1 one.user.info invoked , -1, false
Thu Nov 11 17:49:21 2021 [Z0][ReM][D]: Req:3472 UID:0 one.user.info result SUCCESS, "<USER><ID>0</ID><GID..."
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:8224 UID:0 IP:127.0.0.1 one.vm.info invoked , 2, false
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:8224 UID:0 one.vm.info result SUCCESS, "<VM><ID>2</ID><UID>0..."
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:3472 UID:0 IP:127.0.0.1 one.zone.raftstatus invoked
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:3472 UID:0 one.zone.raftstatus result SUCCESS, "<RAFT><SERVER_ID>-1<..."
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:7760 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:7760 UID:0 one.vmpool.infoextended result SUCCESS, "<VM_POOL><VM><ID>2</..."
Thu Nov 11 17:49:23 2021 [Z0][AuM][D]: _authenticate: -
Thu Nov 11 17:49:23 2021 [Z0][Lis][I]: Stopping
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:832 UID:0 IP:127.0.0.1 one.userpool.info invoked
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:832 UID:0 one.userpool.info result SUCCESS, "<USER_POOL><USER><ID..."
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:4384 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Thu Nov 11 17:49:23 2021 [Z0][ReM][D]: Req:4384 UID:0 one.vmpool.infoextended result SUCCESS, "<VM_POOL><VM><ID>2</..."
Thu Nov 11 17:49:24 2021 [Z0][AuM][D]: _authenticate: -
Thu Nov 11 17:49:24 2021 [Z0][Lis][I]: Stopping
Thu Nov 11 17:49:24 2021 [Z0][ReM][D]: Req:8432 UID:0 IP:127.0.0.1 one.vmpool.info invoked , -1, -1, -1, -1, ""
Thu Nov 11 17:49:24 2021 [Z0][ReM][D]: Req:8432 UID:0 one.vmpool.info result SUCCESS, "<VM_POOL><VM><ID>2</..."
Thu Nov 11 17:49:26 2021 [Z0][ReM][D]: Req:336 UID:0 IP:127.0.0.1 one.user.info invoked , -1, false
Thu Nov 11 17:49:26 2021 [Z0][ReM][D]: Req:336 UID:0 one.user.info result SUCCESS, "<USER><ID>0</ID><GID..."
Thu Nov 11 17:49:28 2021 [Z0][ReM][D]: Req:672 UID:0 IP:127.0.0.1 one.group.info invoked , 0, false
Thu Nov 11 17:49:28 2021 [Z0][ReM][D]: Req:672 UID:0 one.group.info result SUCCESS, "<GROUP><ID>0</ID><NA..."
Thu Nov 11 17:49:30 2021 [Z0][ReM][D]: Req:6208 UID:0 IP:127.0.0.1 one.user.info invoked , -1, false
Thu Nov 11 17:49:30 2021 [Z0][ReM][D]: Req:6208 UID:0 one.user.info result SUCCESS, "<USER><ID>0</ID><GID..."
Thu Nov 11 17:49:30 2021 [Z0][ReM][D]: Req:1328 UID:0 IP:127.0.0.1 one.group.info invoked , 0, false
Thu Nov 11 17:49:30 2021 [Z0][ReM][D]: Req:1328 UID:0 one.group.info result SUCCESS, "<GROUP><ID>0</ID><NA..."
Thu Nov 11 17:49:34 2021 [Z0][MKP][D]: Marketplace TurnKey Linux Containers (2) successfully monitored.
1 Like

Hello

I have the same problem when accessing with VNC. “tunnel_error”

Have you solved it?

After testing, I have decided to install virt-viewer to access the VM console. It works, but it’s not as comfortable as VNC on the web :upside_down_face:.

1 Like

Hello @Franco_Diaz and @fruiti,

Actually, Sunstone needs the FireEdge server to use Guacamole for remote connections. You can read more about how to configuration in documetation.

You can check if the FireEdge server is up and the log file: /var/log/one/fireedge.log

Best, Sergio

2 Likes

Hello @sbetanzos,

I had skipped the FireEdge configuration.
It works perfectly.

Thanks :grin:

1 Like

No I have returned to On v5.12 wich use noVNC solution.

Hi @sbetanzos. I installed ON inside an LXD container, inside a baremetal host. The FireEdge is installed by default and I think…it use the 127.0.0.1
:public_fireedge_endpoint: http://127.0.0.1:2616
This didnt work for me.