Search results

Are you testing with KVM or are you testing with LXC? With containers it works fine, you need to open a console session to a KVM VM. The contents of /etc/hosts is fairly standard. 10.12.1.217 proxmox01.redacted proxmox01 pvelocalhost 10.12.1.218 proxmox02.redacted proxmox02...

It's identical behavior on all browsers on the OSX platform (FF, Chrome, Safari). It also happens with the same browsers on Windows as well as internet explorer/edge. I can't set up a cluster where this doesn't happen, going all the way back to 3.4.

Any thoughts proxmox team? :)

Nothing exotic. We're still on the original self signed certificates. EDIT: If I setup a default cluster with a new install, I also see the behavior with KVM. I don't think it's a case of expired/invalid certificates.

Another data point for this problem. On the same cluster where this breaks for KVM, it works fine for LXC. It must be something associated with the NoVNC subsystem. Any help would be appreciated.

Thanks. Here's the reference. Bug 1160 - 4.3 ha-manager attempts to start kvm templates resulting in ha migration failure https://bugzilla.proxmox.com/show_bug.cgi?id=1160

I'm not entirely sure what that has to do with what I'm asking. VM Template (KVM) _is_ a VM, it is stored on a central GlusterFS cluster. The only difference is that the template cannot be started. You cannot create linked clones without a template, and you cannot create instantaneous clones...

New thread here as requested. https://forum.proxmox.com/threads/pve-4-3-console-access-on-different-cluster-member.29733/

Somewhere around version 3.4, the default behavior for opening consoles across a cluster changed. If you have a three node cluster, and are currently connected to say node01, the UI will generate authentication errors if you attempt to connect to a VM on any other node. In the past, this used...

Has anyone ever resolved this issue? It's still present in 4.3 except with a fresh error: Unsupported security types: [object Uint8Array] Note, I can produce this consistently if I connect to a pve cluster via node1, while trying to open console on node3. It's quite awkward to have to keep...

Team, I'm currently working on an application that utilizes a multi-node proxmox cluster to serve template VMs to a variety of users. The VMs that are served, are all linked clones. In previous versions, if a node were to fail, HA would migrate the templates to the remaining nodes...

More importantly it's not just about the management interface, it's about having a common IP address for the cluster API service. Big upvote ;-)