Search results

I have the solution (based on an answer on another thread). It was being blocked by ESET security. Even if you try "pause firewall/allow all network traffic" that does nOT pause the TLS filtering in ESET. You have to turn that off here

That WAS the problem. I thought that it was not ESET because I had tried "pause firewall/ allow all network traffic" and that made no difference. turns out that "allow all network traffic" does NOT stop the TLS filtering! This is what you have to turn off:

ok...I am now officially confused as hell. Adding exception in eset (which I do use) did not help stopping eset totally did not help clearing chrome cache did not help I found another laptop that had not been powered up in maybe two months. Fired it up, stopped eset so it would not update - and...

I had already tried updatecerts --force. Just tried again. the 25% success rate is random. does not matter which node I am connecting on vs node running vm. i.e. on gui for node04, I can connect to console on one vm out of ten right now, all running on that node

I tried disabling everything. I also found today that if I connect with firefox in private mode I can connect to console on maybe 25% of the VMs. It totally fails in chrome, ie, edge and safari. so...I am certain it is on the server end. But since some of them have not been updated in months...

A bit more info. using firefox, private mode it does work on some VMs - about 25% of them. the rest are blank screen. I think there are two problems: 1) reported by many people is this issue with consoles not working. you can connect, but no display 2) what I first reported. chrome, ie...

I saw a mention of that...but for some reason firefox will not connect to the gui at all. ok - just got it to connect to the gui by using private mode. And this does seem to go a step further - instead of "failed to connect to server" (with a JS cert error) it DOES connect, but is not working...

I tried chrome, ie, edge, even safari I have two clusters - one still on 5.1 the other on 5.4 (latest 5.x) both fail the same way

any updates on this issue? I have the same problem - two different proxmox clusters. 5.1-36 and 5.4. Upgraded one node to latest everything and rebooted. Note that this failure is on all node shells, all VM consoles. Nodes that have most recent update. nodes out of subscription that have...

4 node cluster running proxmox 5.1-36 Suddenly I cannot connect to VMs or node shell via novnc. It fails to connect to service. js console shows: app.js:4696 WebSocket connection to 'wss://{redacted host...

and...getting weirder. I just did 6 restores on one server that had no other existing VMs. East restore took longer, and load and IO delay went higher. This was without even starting the VMs. Just restore, then again, then again, creating multiple new VMs. Then I tried doing a restore to an...

I do not think it does have to do with chunk size or anything like that. It is something more...profound. two things to consider: 1) as I said, the high load occurs AFTER the restore hits 100%, and has at that point finished writing the disk image file to the volume. It is only about 16...

I am in the process of upgrading a cluster from proxmox 3 to 4.3 I am doing the upgrade by migrating all VMs off a node, removing that node form the cluster and doing a clean install of 4.3, partly just so it is clean, partly because I am changing how I am setting up the volumes for VM disk...

I am adding a service that requires port mirroring. i.e. if all my VMs were physical servers I would set up port mirroring on the network switch, sending all matching traffic to/from certain physical switch ports to one port, where software running on a different server would capture it. I...