Recent content by binaryanomaly

Thanks. Works. Same fix as I did manually.

This exactly what happened. Upgraded to debian 13.1 and suddenly stopped running after restarting the container. Shouldn't happen, should maybe raise a warning but not blocking the start.

This is not a very robust way of doing things Proxmox / @t.lamprecht ... Stuff like this should soft-fail and not suddenly completly prevent legitimate containers that just have been updated - from being launched with a not so clear error message.

I wanted to point this out... ;) Also I'd certainly prefer a properly engineered solution by proxmox. But then I'm only wishing for things here. :)

Nice, this should be integrated as a proper feature. @proxmox staff: Any chance this gets included?

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...