Search results

Over in our bugzilla would be right place, but check if something has already been reported (for example [2]). [1]: https://bugzilla.proxmox.com/ [2]: https://bugzilla.proxmox.com/show_bug.cgi?id=6777

Thanks, we are aware of this and a fix is being worked on. Thanks for reporting this to us, though!

I doubt this is an issue just due to the color scheme, but if you want to change it, clearing the cookies and making sure your system prefers light color schemes should work. Can you post the output of pveversion --verbose and als the output of apt policy please? Also please check if the...

Good point, I guess some bookworm based installations have already switched to the new deb822 format. In that case you need to adapt the .sources instead. However, running apt update and then apt policy should always show you the currently configured repositories. So checking that, especially...

Sounds a bit like Chrome is not handling the cookies correctly there. Maybe something is interfering there, but hard to tell from the information provided. You need to check what exactly each request is doing in the network tab of the developer tools of the browser. It's a bit tricky to walk you...

Did you make sure to reboot the server and refresh the user interface with CTRL+SHIFT+R? What does your journal say when you try to log in and load a page? Could you also tell me whether you have any errors in the browser's consoles? That is typically accessible by pressing F12 and selecting...

You have Bookworm and Trixie repositories configured. Please remove the bookworm repositories and configure Debian Trixie repositories correctly. Otherwise, the upgrade cannot work. You seem to be using a local mirror, make sure that it also contains the Debian Trixie repositories. The output of...

Hey, How did you upgrade the packages? With apt dist-upgrade? Also, can you post the output of the following commands? apt policy pbs3to4 --full proxmox-backup-manager version --verbose Thanks!

No problem, if your issue has been resolved, please mark this thread as “Solved” by clicking the “Edit Thread” button on top and adding the “Solved” prefix. Thanks!

Ah sorry i missed that before, but you only seem to have Proxmox VE repository installed, not a Proxmox Backup Server one. Install it with the following command: cat > /etc/apt/sources.list.d/proxmox.sources << EOF Types: deb URIs: http://download.proxmox.com/debian/pbs Suites: trixie...

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