Input lag using NoVNC Console

[gfngfn256]

So PVE is listening out on the port.

Try & find maybe something that is blocking traffic on port 3128, Windows firewall, router, switch etc.

A test you could make, spin up a Linux OS (Debian?) + Desktop VM, set it up for SPICE, & see if that connects.

 

[Exio]

So PVE is listening out on the port.

Try & find maybe something that is blocking traffic on port 3128, Windows firewall, router, switch etc.

A test you could make, spin up a Linux OS (Debian?) + Desktop VM, set it up for SPICE, & see if that connects.

Hmm, i have a Ubuntu VM and SPICE still not working with that VM. Im thinking that im from the A point of an VPN and the Proxmox server is in B point. It have to be some firewall thing but... where should i open that port? In A or B?

 

[gfngfn256]

Hmm, i have a Ubuntu VM and SPICE still not working with that VM. Im thinking that im from the A point of an VPN and the Proxmox server is in B point. It have to be some firewall thing but... where should i open that port? In A or B?

Have an idea to see if that's the problem. It will depend on the exact/config NW you have setup (so this may not work).

From within the Ubuntu VM access your PVE instance & try & connect to your Windows VM via spice from there.

So in effect you'll be working from within the "B" point. Its worth a try.

It probably won't be good for a speed/lag test (your original problem) due to the amount of virtualization nesting going on - but at least you'll have an idea where to go from here.

 

[gfngfn256]

Don't know your NW setup/config HW/SW - but my guess/hunch is - when you get sorted with the current SPICE problem, you will probably discover the reason for your original lag/latency problem.

 

[Exio]

From within the Ubuntu VM access your PVE instance & try & connect to your Windows VM via spice from there.

Indeed, it lets me access this way

The problem now is how to identify what causes the connection error, Proxmox firewall, router firewall, configuration of Wireguard....?

 

[gfngfn256]

The problem now is how to identify what causes the connection error, Proxmox firewall, router firewall, configuration of Wireguard....?

Now inevitably you've got to go down that rabbit hole!

What I would do in your position:

• Draw up a Network diagram of your entire hierarchy (this is always invaluable info - for configuration / problem solving / updating). There are plenty of online helpers (if you need) to get this job done - easily. You can also use just good-old pen & paper!
• Start going through every connection point - on a line connection between your client & host.
• Work out what that connection point is doing & how.
• Assess whether that could be the point-of-failure for the port block.
• Making necessary changes to that connection point.
• Go to the next-in-line connection point & repeat as necessary.

You'll soon find the problem/s. Good luck & hunting.