Search results

I think [1] should mention everything, for a complete overview you can take a look at [2], the structs/enums there describe all available fields and possibly formats they expect. [1] https://pve.proxmox.com/wiki/Automated_Installation [2]...

Yes, you can use the link-local address of the gateway as the default GW for the host, this is common practice. VMs then have the hosts Global Unicast Address as their gateway. Just make sure ipv6 forwarding is enabled on the host. # add this to /etc/sysctl.conf net.ipv6.conf.all.forwarding=1...

Hey, die Einträge sind alphabetisch geordnet, also A, B, C, ... > a, b ,c , ..., alles mit Kleinbuchstaben kommt nach dem letzten der mit Großbuchstaben beginnenden Einträge, C:\Windows\System32\config sollte in der Liste sein, nur halt etwas weiter unten. edit: Könnte mir auch vorstellen...

Could you iperf3 -s in the VM and iperf3 -c <VM_IP> in the container? You might have to start the container with docker run --network=host ...

Hey, I see you have both interfaces as bridge ports, but since they are on the same network, this doesn't really have any benefit, it'll actually will probably cause problems. You can either only use one, or configure a bond and have the second one as a backup, that would look something like...

Hey, how is the packet loss? A bit of a wild guess, but is it possible the configured MTUs along your network don't always match up, other than that I can't really think of anything that might explain this, since the speed is fine for the VM itself. Have you tried different docker images, do...

Do you have a firewall configured either on PVE, or your router?

So ping 192.168.50.1 fails? Just to be sure, your router is 192.168.50.1, right? Can you ping any other devices on 192.168.50.0/24?

after ip addr flush dev enp2s0 ifreload -av enp2s0 still has two IPs assigned to it? If that's the case, I don't see how that is possible since PVE does not do any DHCP, so it does not matter what is set on the router. Could you also remove the entry for the PVE on your router.

Is the NUC where PVE runs on? PVE does not get its IP from DHCP, it is specified statically in /etc/network/interfaces. Did you do any network configuration aside from /etc/network/interfaces?

The picture does not match the text, which is the state right after the two commands? enp2s0 should not have an IP assigned to it, only vmbr0 should have one.

Hey, what is the output of ip a after ip addr flush dev enp2s0 ifreload -av ?

Hey, any idea how enp2s0 ended up with two IPs? It should have none, since vmbr0 has an IP. Could you run ip addr flush dev enp2s0 to remove the IP addresses assigned to the interface directly, and ifreload -av to reload everything. Does ifreload complain about anything?

Did you modify the code? You can reinstall the UI packages with apt install --reinstall pve-manager proxmox-widget-toolkit libjs-extjs that should fix the problem.

Hey, does the browser console show any errors/warnings? Do you have the same problem with different browsers?

Hey, have you tried using OVMF (UEFI) as BIOS with TPM and pre-enrolled keys?

Hey, leave it, it is self signed and will only be used if no other certificate is available. IIRC you can't even remove it through the UI.

Hey, nicht direkt im Task selbst, aber mit systemd kann man das so machen, dass nach dem Start/Restart vom pmgproxy.service auch nginx neu gestartet wird, heißt aber, dass nginx hin und wieder unnötig neugestartet wird, da ja nicht jeder pmgproxy Start mit einem neuen Zertifikat zusammenhängt...

Hey, bridge-vids should be space separated[1], the rest looks fine, if I didn't miss anything. IIRC ifreload -a -vv should yell at you for that, may be helpful to spot things like this. edit: actually doesn't [1] https://manpages.ubuntu.com/manpages/jammy/en/man5/interfaces-bridge.5.html

That is only the case if you login as the root user. But no, something like that is not on our roadmap, if you think you have a use-case for it, feel free to open feature request at [1], since that's where we track those things. [1] https://bugzilla.proxmox.com/