Search results

Hi, I would try another storage (faster) for the VM disk/image, to see if the timeout might be due to slow storage.

Hi, Did you check the HDD disk using smartctl? the `input/output` error might sometimes to hardware issue.

Maybe the reason of that, that host CPU ensures full compatibility with updates. and some CPUs works, but future updates could still fail due to missing CPU features. [0] [0] https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_meltdown_spectre

I mean, try to install Firefox using `apt install firefox-esr` for example

Hi, Did you test with traceroute tool? `traceroute google.com`

To narrow down the issue, I would ask: - Only a specific VM have the issue mentioned? - Did you double-check of the VM config specifically on the bandwidth? -What kind of the network you use in your node SDN, or OVS? - Did you test `iperf3`? - Additionally, what version of Proxmox VE are you using?

Hi, I guess there is a request for that in our Bugzilla [0] you can add CC to yourself to get update. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=2424

Hi, I would check `/etc/hosts` file on both the new and existing nodes has consistent and correct entries. Each entry should map both the public IP to the FQDN and the private IP to the short hostname, additionally, could you run the following command from the both nodes? curl -k...

Have you tried to install the Firefox using apt instead of deb?

Hi, To avoid issues such as clock skew errors make sure that your nodes use chrony [0]. If the chrony is installed and up and running, I would check the syslog and ceph log for more details. [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_time_synchronization

This looks a Browser issue, not related to Proxmox VE. I would check the error you get when you try to browse. Maybe a Proxy?

Great! Glad to hear that you solved the issue yourself! I will go ahead and set your thread as [SOLVED] in order to help the other people who have the same issue.

Hi, Even `host` CPU type didn't help? If yes, I would check if the VirtIO have an update.

Hi, No. I would remove the unused disk `unused0: vm-storage:vm-100-disk-1` and re-run the replication. make sure that you have a valid backup of the VM before.

Hi, Since the two subnets are behind the same router and can ping each other, you should able to access to the Proxmox VE from the 11.0/24 subnet. I would check if there is a firewall on your router side or Proxmox VE side.

Hi, Did you see anything in the syslog when the VM got a crash? May also please provide us with a screenshot to see what exactly do you mean with `white screen`? Could you also tell us where do you see the white screen in the Windows installation or where exactly? Have you tried different...

Hello, This is not a Proxmox related. However, it's common for generic firewall applications, like the Intel N100 Mini PC you've acquired, to lack comprehensive docs, especially when sourced from manufactures without extensive support resources. I would utilize general guidelines and community...

Thank you for the output! I don't see anything related to the issue in the above info you've provided..... I would check if `igb` NIC have an available firmware update.

Hi, Have you tried to re-add the shared storage to your other nodes? If not please give a try! I would do the exact same as the deleted node from the cluster config.

Hi, 2024-11-21T10:24:46.980889+00:00 PBS1 proxmox-backup-api[146]: authentication failure; rhost=[::ffff:192.168.1.11]:49716 user=backup@pbs msg=Unable to acquire lock "/etc/proxmox-backup/tfa.json.lock" - Resource temporarily unavailable (os error 11) 2024-11-21T10:24:49.982360+00:00 PBS1...