Latest activity
-
Jjixuuse replied to the thread [SOLVED] Is the global welcomelist really effective?.The use of traditional whitelists has solved the problem, and old methods always work, don't they.
-
-
DHallo zusammen, ich plane, meinen bisherigen lokalen Proxmox-Server in ein Rechenzentrum zu stellen. Es stehen drei öffentliche IPv4-Adressen zur Verfügung. Ich frage mich, ob ich wirklich eine pfSense als VM brauche oder ob Routing/NAT direkt...
-
Ppixler replied to the thread Missing drives on new install --- how to add ?.Thanks for the reply, however I was not able to locate Node > Disks in the menu ... I did however finally have luck using this cmd root@pve:~# wipefs --all --force /dev/sd X .... now the drives showup in the pull down on LVM
-
Fflames reacted to cwt's post in the thread Way more NAGware, very little functionality, bugs galore with
Like.
I believe both points are valid to a certain extent. It is entirely reasonable that Proxmox developers are compensated for their work, and subscription models are clearly appropriate for production environments. The concern many users express is... -
PPsilospiral posted the thread [SOLVED] PVE loses network connection after kernel upgrade to proxmox-kernel-7.0.0-3-pve in Proxmox VE: Networking and Firewall.Greetings Forum, Running PVE 9.1.9 on a Dell T630 & a Dell T620. After a recent upgrade, no network connection. When booting into proxmox-kernel-6.17.13-6-pve from GRUB, network functions normally. When booting proxmox-kernel-7.0.0-3-pve, 'ip...
-
Bbossanova808 replied to the thread Opt-in Linux 7.0 Kernel for Proxmox VE 9 available.I'm a relative novice with this stuff, so please excuse this noise if I am wrong, but that ^ smells a lot like: https://forum.proxmox.com/threads/asymmetric-tailscale-speed-issue-with-kernel-7-and-multiple-nic-types.183574/
-
Ssomebodyoverthere reacted to Freedbot's post in the thread [TUTORIAL] OpenWRT LXC "Forbidden Router" with Like.
Purpose Inspired by Level1Techs, I decided to replace my old router with a single box solution that's flexible, upgradable, and efficient. That includes using Proxmox to utilize spare resources without interfering with the vital router...
-
Ssomebodyoverthere reacted to Freedbot's post in the thread [TUTORIAL] OpenWRT LXC "Forbidden Router" with Like.
Creating the OpenWRT LXC Container Installing OpenWRT into a container requires downloading a special build and installing it via Shell. Sadly, we can't use the Create CT button because there's no setting for an "unmanaged" OS type, and the...
-
Ppixler posted the thread Missing drives on new install --- how to add ? in Proxmox VE: Installation and configuration.Did a new install of 9.2.2 as a test / learning session today, but stuck trying to add 2 x HD sda & sdb ... PVE is on sdc I think I'm in the correct menu to add the drives, but none listed in the pull down (see attached) Looked up some...
-
-
Ddarkseer replied to the thread Multipath iSCSI problems with 8.1.I am still experiencing this in the latest release. I have opinions about this but my short term bandaid is here. YMMV, I hope it helps someone else. For me its that I run apps on truenas. It advertises a whole bunch of internal network iscsi...
-
AAleXSR700 posted the thread PVE becomes unreachable via ethernet but OS is running in Proxmox VE: Networking and Firewall.Hi everyone, I am new to PVE but have setup most things I wanted in my test PVE. Unfortunately, the PVE itself and all VMs/LXCs become unreachable via ethernet from time to time and become immediately reachable again as soon as I log in on the...
-
Aawado replied to the thread [SOLVED] Kein TOTP-Login mehr möglich nach Zeitfehler.Ok, dank KI & OpenCode konnte ich die Ursache jetzt doch selbst finden (lassen): In "/etc/pve/priv/tfa.cfg" wurde der Zugang gesperrt mit …"totp-locked":true… . Wenn man dort das auf "false" setzt, geht es wieder. Ich lass den Post mal so stehen...
-
Aawado posted the thread [SOLVED] Kein TOTP-Login mehr möglich nach Zeitfehler in Proxmox VE: Installation and configuration.Ich wollte auf einem Hetzner Dedicated nun endlich mal das Upgrade zu PVE 9 machen. Bei den Vorbereitungen über SSH fiel mir auf, dass die Systemzeit nicht stimmt und deswegen der Login in der Proxmox-Weboberfläche nicht mehr per TOTP möglich...
-
PProxonaut replied to the thread Proxmox install on Minisforum ms-01.So they heats up quick are you saying that usually ?
-
Ccelemine1gig replied to the thread Started getting this warning on a VM where I pass through a SATA controller on proxmox 9.2..It might be, that feature compatability between QEMU and kernel version "causes" this message. That means one side trying to use a feature that the other cannot deal with. Easy to try out, if you are right with your assumption. Looking forward to...
-
Fdid you solve it? (since it says 'SOLVED' in the tile) if yes, what was the problem? maybe someone else can profit from your solution
-
Sslavik-f replied to the thread Proxmox 9.2 installer hangs: waiting for /dev to be fully populated.1. I think that because of NovaCore, the Proxmox 9.2 doesn't work with Nvidia RTX cards. `nomodeset` doesn't help. 2. In some cases, during upgrade, something is failing / misconfigured with the network stack, so even SSH access is not available...
-
Ccelemine1gig replied to the thread Started getting this warning on a VM where I pass through a SATA controller on proxmox 9.2..The kernel version is irrelevant, if you answer none of the other questions. Here is the exact code line where this is coming from: https://github.com/qemu/qemu/blob/master/hw/vfio/region.c#L324 Same code is not included in QEMU 10.1...
-
Ffranko5 reacted to cyrenbyren's post in the thread Console ends up with "connection timed out" with Like.
I'm using a single dns entry (as PVE is a consul service in my network), to point to all the nodes in my proxmox cluster. All of them have their own unique SSL certificate, but all of them also have a common name (let's call it pve.my.domain)...
-
Ccelemine1gig replied to the thread Started getting this warning on a VM where I pass through a SATA controller on proxmox 9.2..And what exactly is the issue here? How often do you see this message? Why does it bother you? As you might have already seen in your search, this start with kernels >v6.19. However, from what I read, it is intended just to be that, a "warning"...
