[SOLVED] Failed to run vncproxy

Jer

New Member
Sep 29, 2017
4
0
1
35
Hi,

I have a two node setup. From the first node, when I pull up the console for a VM on the second node, I get this:

Debian GNU/Linux 9
Permission denied (publickey).
TASK ERROR: Failed to run vncproxy.

I can't tell if this is an SSH issue or a vncproxy issue. I have verified that the authorized_keys are set properly to match the ssh keys on each host.

Any idea on troubleshooting this? Proxmox version 5.1-41.

Thanks!
 
Last edited:
Okay, I figured it out. I did a stupid and disallowed root ssh access.
 
hi,

how did you solve the issue? could pls provide the steps?

I came across a similar issue.

From my logs:
Code:
Jan 16 21:23:36 pve01 pvedaemon[20292]: starting vnc proxy UPID:pve01:00004F44:00017148:5C401158:vncproxy:100:root@pam:
Jan 16 21:23:36 pve01 pvedaemon[3706]: <root@pam> starting task UPID:pve01:00004F44:00017148:5C401158:vncproxy:100:root@pam:
Jan 16 21:23:36 pve01 pvedaemon[20292]: Failed to run vncproxy.
Jan 16 21:23:36 pve01 pvedaemon[3706]: <root@pam> end task UPID:pve01:00004F44:00017148:5C401158:vncproxy:100:root@pam: Failed to run vncproxy.

The hint of root ssh access by the original poster caused me to stumble upon the solution.

My problem was when I tried to access the console from the WebUI for one host for a VM on another host. The fix for me was to open the web ssh console (Shell) on the other hosts from the WebUI of the primary host. When I did, I was greeted with a prompt to accept the SSH fingerprint. I suspect this was the problem to begin with. As soon as I accepted the fingerprint, I was able to see the console on other hosts.

In fact, I was able to validate it since I still had more hosts in the cluster. After entering the UI through another host, the problem was back. The fix was as I described above. I recorded the fix in action, but cannot post links as a new user:

You can find it here: imgur.com/5V8CmKK.gifv