noVNC (not VNC) console: Login to Proxmox host failed

Discuss our WHMCS modules and everything associated with them.

noVNC (not VNC) console: Login to Proxmox host failed

Postby papak011 » 26th July 2016, 5:26 pm

2016-07-26_15-10-20.png
2016-07-26_15-10-20.png (38.02 KiB) Viewed 6377 times
Hi,

We use Proxmox for vPS in WHMCS. Since we are on Proxmox 4.2 login to noVNC console doesn't works: : "Login to Proxmox host failed". We tested the connections and everything works except noVNC. We can reboot, stop, start VM, see Graphs etc. through WHMCS but clicking on noVNC console we see error message as on attached picture. We have latest module Version but in the package under folder 'UploadOnProxmoxServer' is not files for 4.2.

We contacted support [Ticket ID: 241921] but he don't know what is noVNC console and give us something about VNC console which we don't use. Blame. :x

Any help would be appreciated.

Regards,
Mike
papak011
 
Posts: 5
Joined: 5th February 2015, 11:11 am

Re: noVNC (not VNC) console: Login to Proxmox host failed

Postby Piotr » 27th July 2016, 3:57 pm

Hello!

If anyone has any idea then feel free to answer ;)

Mike, it appears that we had a little communication problem in ticket #241921. I just wanted to let you know that your ticket has been escalated to the next level support and it is awaiting now for verification by our Tech Support Team Leader, Damian. Hopefully we will find a solution shortly.

Have a nice afternoon!
Piotr Dołęga
ModulesGarden CMO
Website Admin
ModulesGarden - Unique Approach To Custom Software Development Services & High-End Modules
User avatar
Piotr
Site Admin
 
Posts: 615
Joined: 14th June 2012, 10:19 am
Location: Poland

Re: noVNC (not VNC) console: Login to Proxmox host failed

Postby cherrywoodtech » 27th October 2016, 4:32 pm

We ran into this problem as well when updated to the latest version of Proxmox. However I ended up running:
pvecm updatecerts -f
This got the issue resolved but then realized that our ssl certs were jacked since this reverts ssl to default. *oops* You could just try:
systemctl restart pveproxy
See if that gets things going properly without using the first command. Otherwise you have to reset up your certs, which actually isn't too bad if you back everything up properly.
cherrywoodtech
 
Posts: 20
Joined: 17th May 2016, 1:32 am


Return to WHMCS Modules

Who is online

Users browsing this forum: No registered users and 6 guests

cron