Call Us! [visitorlocation]
Call Us! [visitorlocation]

Need Help?

Our experts will login to your server within 30 minutes to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Proxmox failed to run vncproxy – Here is how we sort it out

Are you getting the error failed to run vncproxy while using Proxmox? We can help you fix it.

Usually, this error occurs due to improper symlink configuration.

At Bobcares, we often get requests to fix errors in Proxmox, as a part of our Infrastructure Management Services.

Today, let’s have a deeper look into Proxmox VNC Proxy and see how our Support Engineers fix this error.

 

VNC Proxy in Proxmox

Proxmox VE is an open-source server virtualization environment. It allows easy managing of VMs, containers, highly available clusters, storage, and network. And we can manage all these using the integrated web interface or via the CLI.

Whereas VNC proxy is the VNC interface for Proxmox VE hosts in the cluster. Once the cluster is set up, it is quite easy to manage it via the VNC Proxy. It provides access to the cluster to anyone with a VNC viewer. That is VNC Proxy is both the VNC client and VNC server.

But what if it shows up error while accessing VM console of other VM? This is a recent error our customer got. The error message appeared as,

Proxmox failed to run vncproxy.

So, let’s see how our Support Engineers fix it.

 

How we fix the Proxmox error failed to run vncproxy?

Initially, we checked whether the VMs are accessible or not. Also, we were able to SSH from one VM to another.

Then we tried to invoke the vncproxy using the command,

/usr/bin/ssh -e none -T -o BatchMode=yes <IP of other VM> /usr/sbin/qm vncproxy $VMID

And this resulted in permission denied error.

Sometimes, syntax error in the command to invoke vncproxy can cause the same error. But this was not the actual reason here.

On further checking, we found that the symlinks were not configured correctly.

So we corrected these symlinks as, * /root/.ssh/authorized_keys to /etc/pve/priv.

Additionally, we check the key-pair in /root/.ssh/id_rsa(.pub). And we ensure that the public key in the pair is in /etc/pve/priv/authorized_keys.  Thereby we ensure that the PVE synchronizes with the cluster.

 

[Need assistance in fixing Proxmox errors? – Our Experts are available 24/7.]

 

Conclusion

In short, Proxmox failed to run vncproxy error occur due to improper symlink configuration. Sometimes invoking the vncproxy can resolve this error. Today, we saw how our Support Engineers fix this error.


PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF