Search results

Interesting, what does apt show proxmox-backup -a report? Also what does the packages.wazuh.com repository provide?

That does not look like PBS 4, you are still running PBS 3.4. Are you sure you followed the upgrade guide correctly [1]? What does apt policy say? [1]: https://pbs.proxmox.com/wiki/Upgrade_from_3_to_4

Can you post the output of the following command: proxmox-backup-manager versions --verbose. Thanks!

Alright, but all you should need to ask them for is a certificate file from the middle box. That should not be specific to Red Hat or anything similar. In theory, you could even use openssl to download the cert like so: openssl s_client -connect releases.turnkeylinux.org:443 -showcerts...

That isn't the TLS certificate but the signature for the aplinfo from what I can tell. Those are separate things. No, this is some middle box. Blue Coat Systems is a provider of security products. Likely you are connecting through something that wants to do some kind of package inspection for...

Are or were you using a specific language before? If so which one? Also does the problem persist after reloading the page with CTRL+SHIFT+R?

That sounds like the certificate cannot be verified. What does openssl s_client -connect releases.turnkeylinux.org:443 return for you? Also are you using some kind of proxy?

No problem, but happy to hear this works again!

Yes the memory accounting logic here has changed. This is more or less expected, see [1]. [1]: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher

Hm this seems to work just fine for me. Can you open the developer console of your browser (typically accessible via F12) and navigate to the “Network” tab and see check what the result for the /proxy request for that widget are? It seems even if you tell homepage to provide debug logging it...

Hi, thanks for reporting this! That's curious, especially given your curl command works just fine. Not sure what homepage is doing here specifically, but I'll try to reproduce this. Can you maybe also post some logs from homepage itself if you have those? If you opened an issue with homepage...

Hi, this should be fixed in PBS 4.0.12-1, hope that helps :)

You should remove the repo from the /etc/apt/sources.list and keep the one in the /etc/apt/sources.list.d/proxmox.source file. The problem with your screenshot is not quite clear to me. You should move the old ceph.list file once the new trixie repo has been activated.

Thanks, yes it does, seems that our regex here does not pick up on this way of naming libsystemd-shared, send a patch: https://lore.proxmox.com/pve-devel/20250806134843.266183-1-s.sterz@proxmox.com/T/#u For now, it should be safe to ignore this warning in this case specifically. Since, this...

Hi, what systemd version does the container use? And what does the command find / -name "libsystemd-shared-*.so" 2> /dev/null return in the container (ideally you could run that as root)?

Can you post the logs of that? The log above look like you can't log in at all: This for example indicates that pam could not authenticate you at all.

I think this is probably unrelated to the issue with pam here though. If I remember correctly, we have changed some dependencies there, but I am not too familiar with the TFA part of our authentication code. Regarding the authentication error - lines, the still occur on PBS 4.0.11 or 4.0.10 for...

Hey again, a couple of questions just to clarify: - You can't log in at all or do you get logged out again immediately after you initially logged in? - Do the log lines with authentication error - SUCCESS (0) still happen when you log in after the update? If so did you reboot the machine? -...

Ok so the somewhat confusing log message makes sense now and I send a patch for it here [1]. I'll look into what exactly is happening here, though. [1]: https://lore.proxmox.com/pbs-devel/20250805154820.324167-1-s.sterz@proxmox.com/T/#u

Thank you, can you try to log in via ssh and update to the latest version right now? Installing from the ISO, it seems that PAM has some problem logging in. Especially this part: authentication failure; rhost=[::ffff:10.10.10.1]:42160 user=root@pam msg=authentication error - SUCCESS (0)...