Search results

Well that may be. But I am seeing this issue regularly - I believe, since the update. Since I can't even ping between VMs/LXCs inside this bridge/network then it's presumably somehow related to proxmox?

Hi, I'm having a networking issue since the upgrade to 7.3: I have a network bridge with no physical port running auto vmbr1 iface vmbr1 inet manual bridge-ports none bridge-stp off bridge-fd 0 #LAN Virtual Bridge 1 which I use for networking between some VMs and LXC...

Thanks. Explicitly setting HostKey /etc/ssh/ssh_host_ed25519_key in /etc/ssh/sshd_config seems to have no effect. Looks a bit like hardcoded UI? legacy to me - as I have not recognized any effect besides that error message in the UI?

Where would I have to do this? I see no explicit reference in the ssh config files. SSH works fine it seems only pve is complaining about it Aug 17 19:33:48 bm-deb-proxmox pvecm[3195]: can't open '/etc/ssh/ssh_host_rsa_key.pub' - No such file or directory

I have a similar issue. I have regenerated the ssh keys and only created a new ed25519 key. Now the UI complains: can't open '/etc/ssh/ssh_host_rsa_key.pub' - No such file or directory (500) Don't need and don't want it. :) Is this somewhere hardcoded in the UI or why am I seeing this? The...

Great, thanks for the swift response @aaron XenForo might be impacted though: https://xenforo.com/community/threads/psa-potential-security-vulnerability-in-elasticsearch-and-more-via-apache-log4j-log4shell.201145/

I'd like to have some information here as well. Thx.

Thanks, that worked here as well (after hours of investigation...).

Thanks. .hushlogin was the problem. Now everything behaves like it should.

Hi, I would like to restore Debian vanilla motd functionality but it seems proxmox has somehow messed with it and I'm unsure of how to restore properly. I have already stopped and disabled the pvebanner service: sudo systemctl status pvebanner ● pvebanner.service - Proxmox VE Login Banner...

Hi, I have a question regarding required mitigation measures against spectre / meltdown / ... on different levels, i.e. what is needed where. As I understand it, already the host OS - Debian contains mitigations according to lscpu output: Vulnerability Itlb multihit: Not affected...

Thanks for the write up. Method 1 here: https://www.xmodulo.com/enable-sr-iov-virtual-function-intel-ixgbe-nic.html is actually much simpler and quicker to enable SR-IOV. Edit: I just found that the intel driver documentation does no longer recommend the above approach.

Thanks, this worked like a charm on an initially debian based installation For those who have only 1 node that runs infrastructure required to access the internet such as Firewall, DNS, etc. it might be helpful to fetch the required packages in advance in order to be able to shutdown the...

I think in terms of efficiency it won't probably matter much whether you use raid1 or ZFS mirror. But if you want to use ZFS then mirror is to be preferred over raid. Of course you can also do raid1 with ext4, etc. Performance of raid1 or ZFS mirror will be as if you have 1 disk and likely good...

As I understand it, if you want to use ZFS as the underlying filesystem the general recommendation is to not use a hardware raid controller but rather leave these kind of responsibilities and duties to the ZFS software only. The raid controller would be a potential single point of failure that...

My board also has an Intel® I219-V 1Gb Ethernet card and everything runs smooth since weeks with Kernel 5.11. $ sudo lspci -v | grep Ethernet 00:1f.6 Ethernet controller: Intel Corporation Device 15fa (rev 11) $ sudo lspci -vnnk -s 00:1f.6 00:1f.6 Ethernet controller [0200]: Intel...

How about having something like deb http://download.proxmox.com/debian/pve buster pve-no-subscription somewhere like: /etc/apt/sources.list.d/pve-no-subscription.list

Ok thanks, hope it won't be long... ;)

Try Kernel 5.11 https://forum.proxmox.com/threads/kernel-5-11.86225/ I have a Z590 MB and the NIC only started working with 5.11.

Hi, I would have expected that the ip(s) of containers would be visible in the web-ui. This does not seem to be the case, why? It would be particularly helpful to see what ip was assigned to a container in the web-ui.