So, I started noticing this weird freezes. While I am typing inside VM console from proxmox GUI, it suddenly freeze. By refreshing page or clicking to different menu item in poromox and clicking back to console start working. I had issue in old latest install. I did complete new install and having same issue.
Proxmox VM console from GUI freezes
- Thread starter ZooKeeper
- Start date
Hi,
Have you tried on a different browser?
Does the Syslog says anything when the console got frozen?
what is the PVE version are you use
Have you tried on a different browser?
Does the Syslog says anything when the console got frozen?
what is the PVE version are you use
pveversion -v ?
Edit: i thought I was typing in windows 10 issue I had. Are you using two IPs?
Last edited:
I've been troubleshooting this for a few days. It's been happening for the past several months.
If your proxmox server is connected to more than one subnet, and has an IP configured on them, I'd look at that.
For me, I had an issue a while back and configured a spare ethernet port to connect to the subnet my computer was on, so I could connect to a local IP to perform network changes. I never removed it... Fast forward, because I normally connect to the proxmox IP that's on another subnet, I guess the network path was being split and causing problems (return packets would come out a different interface because it was local). As soon as I removed that IP from proxmox on my local subnet, the issue went away.
FYI, I was able to reliably reproduce the freeze by watching a video in the proxmox VM console and keep moving the mouse around. It would consistently freeze after about 50 seconds. No more!
If your proxmox server is connected to more than one subnet, and has an IP configured on them, I'd look at that.
For me, I had an issue a while back and configured a spare ethernet port to connect to the subnet my computer was on, so I could connect to a local IP to perform network changes. I never removed it... Fast forward, because I normally connect to the proxmox IP that's on another subnet, I guess the network path was being split and causing problems (return packets would come out a different interface because it was local). As soon as I removed that IP from proxmox on my local subnet, the issue went away.
FYI, I was able to reliably reproduce the freeze by watching a video in the proxmox VM console and keep moving the mouse around. It would consistently freeze after about 50 seconds. No more!
Greets and Happy belated New Year! I just started having problems with a 4 node cluster running different machines - NEVER had console or terminal issue until just recently (only added a new switch to the network) - now when I open a console from the Proxmox GUI - or start a console with VNC or Spice - no matte whether it's a VM console or not - the console freezes up after an undetermined amount of time - just stops working.
There doesn't seem to be and errors or logs showing something wrong!! Oddly enough, my setup was working fine for over a year without issue, but now it's become unreliable ?!?!? Any hints welcome!!
There doesn't seem to be and errors or logs showing something wrong!! Oddly enough, my setup was working fine for over a year without issue, but now it's become unreliable ?!?!? Any hints welcome!!
Thanks Luckyj for your response - YES, I have multiple IPs assigned to different VLAN segments (see attachment) and that has worked fine since over 14 months - not the issue. Turns out, after many tests - my main machine which I use to access was in the wrong VLAN segment - so this issue only affected ONE machine and Proxmox seems fine - So my bad for jumping to conclusions something was wrong with the servers 
Thanks again and have a great day!
Thanks again and have a great day!
I had the same problem.
Since I connected several additional interfaces, I've always had these freezes.
Previously there was only one (server network), now I had to add three more because I set up my backup firewall as a VM.
I had assigned each interface its IP, which it should have within the VM. From then on, the freezes.
Now I've removed the CIDRs (left them empty) - the firewall is still working fine (the IPs are configured internally) and I've had a terminal window open for half an hour and nothing has frozen!
The only assigned IP (including subnet) is the server network, in which Proxmox itself is located.
So: 4 adapters, 4 bridges; only 1 IP assigned for a bridge, which I use (via browser) to connect to the poor VMs that don't (yet) have a network.
Since I connected several additional interfaces, I've always had these freezes.
Previously there was only one (server network), now I had to add three more because I set up my backup firewall as a VM.
I had assigned each interface its IP, which it should have within the VM. From then on, the freezes.
Now I've removed the CIDRs (left them empty) - the firewall is still working fine (the IPs are configured internally) and I've had a terminal window open for half an hour and nothing has frozen!
The only assigned IP (including subnet) is the server network, in which Proxmox itself is located.
So: 4 adapters, 4 bridges; only 1 IP assigned for a bridge, which I use (via browser) to connect to the poor VMs that don't (yet) have a network.
Attachments
Amazing, I just test this solution, and so far nothing freeze...I had the same problem.
Since I connected several additional interfaces, I've always had these freezes.
Previously there was only one (server network), now I had to add three more because I set up my backup firewall as a VM.
I had assigned each interface its IP, which it should have within the VM. From then on, the freezes.
Now I've removed the CIDRs (left them empty) - the firewall is still working fine (the IPs are configured internally) and I've had a terminal window open for half an hour and nothing has frozen!
The only assigned IP (including subnet) is the server network, in which Proxmox itself is located.
So: 4 adapters, 4 bridges; only 1 IP assigned for a bridge, which I use (via browser) to connect to the poor VMs that don't (yet) have a network.
And I have my computer, on a different subnet that the Proxmox Management, that is what I allways looking for.
Thanks a lot, and I wish somebody can explain what is the problem in the network definition that created this issue publishing the subnets