Search results

This is probably because of the PVE firewall [0]. You may an exception to allow your mDNS traffic to the VMs. [0] https://pve.proxmox.com/wiki/Firewall

No, the PVE can't help you in this case. If you don't want to set up a DNS server, the simplest solution would be to edit your /etc/hosts file (Linux) to include your desired names and corresponding addresses. In Windows and MacOS there is a similar file - just ask your favorite search engine :)

I can not reproduce your problem. In my case, I can reach my node GUI via the hostname. The only thing that comes to my mind is, that there perhaps is some ssl/tls inspection going on (by the browser, or some firewall in between). And this inspecting entity forbids self-signed Certificates for...

Depending on your task, a snapshot or backup of the whole guest would be the easiest solution. The corresponding GUI entries may be found under the guest you want to backup/snapshot and there under either "Backup" or "Snapshots". If you are doing something dangerous inside the VM (e.g. windows...

From my experiments at my own setup I can tell, that you may use the license key as often as you like, with the only restriction, that it is only active on one device at a time. Meaning, that adding the license key to a new machine will invalidate the same key on any older machine which used...

There are already very strong opinions on IPv6 and if it should be disabled by default or not in this forum [0]. I understand your point, but (sadly) this is simply how SLAAC works... Assigning addresses automatically without asking - which in most cases is very useful. By disabling SLAAC by...

Ballooning needs also to be supported by the VM. Linux guests already support ballooning out-of-the-box. For Windows VMs some drivers are needed [0]. [0] https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers

You can use the PVE API to get the same statistical data which is used in the front end [0]. There, the disk and network usage of each VM is recorded via RRD [1]. The API is available in some formats, including JSON, and via pvesh [3] you may use the api via a normal shell. Some endpoints...

Yes, this is theoretically possible. You would have to swapoff -a, remove the swap entry in /etc/fstab, delete the lvm swap LV (logical volume) and extend the root LV and its FS. There are plenty of tutorials online on how to such operations on LVM environments (e.g. Step 4+5 of [0]) - ask your...

Hi, 1.) Das PVE kapiert erst nach einem Herunterfahren und Neustarten der VM, dass du die Einstellungen geändert hast (orange heißt da, dass es applied wird, sobald das möglich ist – in dem Fall, wenn die VM heruntergefahren wurde) 2.) Mit NoVNC geht das leider nicht, mit SPICE allerdings...

I assume, this has to do with Nextcloud config or web server config. There might is a "virtual host" (Apache term?) or something similar and this option may be hard coded to the IP address.

There is your problem. If the system has multiple default routes, the one with lowest metric will be used, in this case 192.168.100.1, see [0]. An ugly fix would be to set the metric manually to a lower value. However it would be better to configure the DHCP server on eth0/1 to not send a...

Do the VMs get a default gateway/default route via DHCP? You can check it with ip route

Oh... there was a small misunderstanding The simplest (and possibly only?) solution would be to edit the remote <host> <port> statement in the exported client configuration file to match your needs. I don't think, that this is possible in the pfSense OpenVPN config, but who knows. Regarding...

Thanks, this makes much more sense to me now :) By "port forward" I mean [a.b.c.d]:1194 -> [192.168.x.70]:1194 on your internet router. So it would be possible to connect via [a.b.c.d]:1194 from outside and probably also from inside.

Thanks for your report :) A patch [0] has already been sent and will be available with the next version (qemu-server >= 6.4-3) [0] https://git.proxmox.com/?p=qemu-server.git;a=commit;h=1cb23b87b40be47c8268b2f8fd6b1505318a507c

Hi, a few things: First, it is in facto possible to boot a live CD in pve: Choose a ISO under VM "hardware" tab and update the boot order under VM "options" tab. The next time you boot up, you should land in your ISO. Second, there are many tutorials online regarding "how to resize/extend root...

You mean, the MAC address is always the right one? Are you sure, there is no other device, that might use your servers ip address anyhow?

Hello, Without a network diagram it's a bit hard to wrap ones head around it, but have you thought of configuring a port forward at your public ip to the PFsense VM?

I think, I found your problem: You imported VM 200, but set the bios for VM 130 The wiki page is written a bit unfavorable, I'll put something like <VMID> there...