Search results

Getting a fully closed case may solve your problem

Ich habe bei mir einen deutlichen Performanceschub gemerkt, als ich das virtuelle TPM wieder entfernt hatte. Keine Ahnung was Windows Server 2025 hier im Hintergrund macht, aber die Performance ist mehr als fühlbar. Ergänzend wäre zu erwähnen, dass die TPM "Festplatten" auf performanten...

Great to hear - I will mark this ticket as solved!

You should check and verify that the new PBS packages available on "test" repository works and solves you problem ;-)

Can confirm that this fixed the problem on my site!

Can confirm that this fixed the problem on my site!

Duplicate of https://forum.proxmox.com/threads/pbs-4-0-openid-not-working.169333/

Hello there, just updated my PVE/PBS server to the newest version and recognised, that PBS is no longer working properly with OpenID login. Initially it allows the login but some seconds later I get back to the login page. On PVE it worked without any troubles. Is this a known bug?

This is what I did: I changed from internal to external domain name which is using the Lets Encrypt certificates and removed the whole fingerprint line. Now everything works as expected.

Additional you also need to do that on a local PBS as well if you change the certificate on a remote

Additional information: If you already had an existing Proxmox Backup Server (PBS) with a manual fingerprint of the TLS certificate you need to edit as well.

Servus @t.lamprecht , thanks - I will give it a try.

Hello there, I have a two node cluster with a QDevice on which my 2nd node also is running PBS. Recently I have been thinking about using a LetsEncrypt certificate for my cluster insteady of the pre generated one but I am unsure if this would kind of "destroy" any trust relationship within the...

I installed a 2nd 2k25 server, updated it until no further update was available and CPU type = host works. So I guess the OP has used an ISO file which does not include the previously mentioned KB package.

Great - thanks and "frohe Ostern" :)

Thanks - that did the trick. Althought it's a bit confusing if "Default (Email)" & "Email (legacy)" are the same. Maybe you can do a cleanup at the next release?

Hello there, I have configured both of my proxmox nodes to use my internal SMTP server and set the default-matcher rule to use it. But day after day I see emails at my inbox where both PBS are using my public IP trying to connect to my SMTP server (which also uses a different public IP): This...

For the time being I just leave the one additional 2k25 DC to see if it's stable so far to migrate the rest of it.

Okay but what is interesting: Even after full patching the version from April 2024 I was not able to use "host" CPU. After installing this KB package I was.

I was using this: 26100.1.240331-1435