Danke für die Zusammenfassungen zum System.
Wenn die Mini PC schon "älter" sind, dann ist bestimmt die WLP nicht mehr zu gebrauchen und ich denke an eine Wärmeproblem.
So dass man evtl. auch mal Temperaturen überprüfen könnte.
You will propably need to change the sources.lists to the archive urls at https://www.debian.org/distrib/archive and
https://archive.proxmox.com/debian/
( see also https://pve.proxmox.com/wiki/Package_Repositories ). Otherwise this should work if...
Found this post from a year ago that fixed it: https://forum.proxmox.com/threads/ipv6-configuration-problem-with-vm-bridge.121404/
You can test it with: echo 0 > /sys/devices/virtual/net/vmbr0/bridge/multicast_snooping
And make it permanent...
PVE7 is based on Debian 11/bullseye, PVE8 on 12/bookworm and PVE9 on 13/trixie.
It seems all 3 repositories you need are still available for both Proxmox and Debian:
http://download.proxmox.com/debian/pve/dists/...
ElectronicsWizardry did some storage testing that really helped me get a handle on what to expect out of VirtIOFS right now.
See: https://www.youtube.com/watch?v=d_zlMxkattE
I actually see this as very useful for getting small files from the...
Hi das passiert eigentlich nur wenn man Spice aktiviert hat und keinen Viewer auf dem Client installiert.
Sonst einfach NoVNC auswählen, das kann jeder Browser.
Danke für die Zusammenfassungen zum System.
Wenn die Mini PC schon "älter" sind, dann ist bestimmt die WLP nicht mehr zu gebrauchen und ich denke an eine Wärmeproblem.
So dass man evtl. auch mal Temperaturen überprüfen könnte.
Hi,
Well, the best practice is not to use public IP on internal network. That is why RFC1918 exists and gave you the possibility to use 3 specific ranges.
Best regards,
Hello Proxmox community,
I’d like to share an open-source project I maintain: Proxbox, a NetBox plugin for synchronizing Proxmox VE infrastructure data into NetBox.
The goal is simple: keep NetBox updated with inventory data from real Proxmox...
Yep, after reviewing the code, I realized that protobuf encoding is not supported. I have opened a feature request.
https://bugzilla.proxmox.com/show_bug.cgi?id=7592
Also wenn da Layer2 und Layer3 lite steht, bezieht sich das auf die Routingfähigkeit des Switch. Layer3 lite, bedeutet nur statische Routen.
Das hat gar nichts mit der Link Aggregation und den LACP Modi zu tun.
Ok, so after a little digging around, my Proxmox Firewall service was reporting the below:
May 18 16:17:11 pve02 proxmox-firewall[5138]: error updating firewall rules: cannot execute nftables commands
May 18 16:17:16 pve02...
like many other sites and pieces of public infrastructure, ours is getting hammered by AI scrapers/bots as well. we try our best to implement counter measures, but it's a constant game of whack-a-mole.
Hi,
Well, the best practice is not to use public IP on internal network. That is why RFC1918 exists and gave you the possibility to use 3 specific ranges.
Best regards,
But thats only for having issues starting a vm on a different node. Im asking because if you add another pci card to a current node. the previous id of the card might change and vm wont boot then?
This is my first attempt using Proxmox, my knowledge is pretty small but I'm still learning.
Probably I should put more effort to understanding the whole Proxmox from the beginning.
But here I am trying from the other side of the table.
Anyway...
like many other sites and pieces of public infrastructure, ours is getting hammered by AI scrapers/bots as well. we try our best to implement counter measures, but it's a constant game of whack-a-mole.
I removed the nvme device, disconnected cd drive, front usb, front card reader etc. then disabled tpm setting (I think that's what it was) in bios. Then problem solved.