Are you stuck with Virtualizor VNC failed to connect to server error? Our Virtualizor Support team is here to lend a hand with your queries and issues.

Virtualizor VNC failed to connect to Server | Resolved

Have you been having trouble with the following error?

Failed to connect 1006 VNC virtualizor

If yes, you are in the right place. One of our customers recently contacted us when one of their nodes with Virtualizor Software had issues accessing VNC.

Our experts were able to narrow down the reason behind the error to a recent Virtualizor upgrade. Fortunately, they also came up with a way to resolve the problem. It involved killing all the processes with the following commands:

[~]# kill $(pgrep -f “/usr/local/virtualizor/enduser/themes/default/novnc/utils/websockify”)
[~]# kill $(pgrep -f “/usr/local/virtualizor/enduser/themes/default/novnc/utils/websockify”)
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec … or kill -l [sigspec]


Alternatively, we have to first stop VPS and restart it from the panel in case VNC was enabled after the VPS was created.

In case, VNC was enabled during VPS creation, we have to ensure the firewall service is not blocking 4081 or the VNC port(59XX).

We can easily verify this by viewing the VNC port in the Manage VPS page while accessing VNC.

In case the error still persists, our experts suggest checking if websockify service is running or not with the following command:

ps aux |grep websoc

In this scenario, we have to install socat package on that server and attempt to access VNC from the panel, and then re-check for websoc process on the master server.

Let us know in the comments which one of the above solutions helped resolve the error.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

To sum up, our Support Engineers took us through different ways to resolve the “Virtualizor VNC failed to connect to server” error.