Search results

alright, this is indeed a bug, there was url decoding missing in the parts of the ui involved here. added that now, the patch for that can be found on the list here [1] and will hopefully be applied soon. thanks for the report everyone! [1]...

Thanks for reporting this. Sorry I got side tracked with other projects before I could tackle this. Yes please open a bug report over at [1]. Thanks! [1]: https://bugzilla.proxmox.com/

Alright so it was just a matter of the PVE host timing out/being to slow for your proxy and the response through your proxy returning a text error page or something like that. Is everything working as intended now? In that case please mark this thread as resolved, thanks :)

Is there a proxy between the PDM instance and the Proxmox VE instance?

Could you post what version is the affected Proxmox VE is running? Thank you!

Interesting, I'll look into setting up a reproducer here. Most of the code between pdm and pbs is shared, though, so really not sure what the difference here would be.

Alright, that's good to know, thank you! Yes, but from my understanding each authorized redirect URI needs to configure specifically. So if you configured it for your other services and not PDM, that could explain why you are running into this issue. Hope that makes sense.

Yes, enabling users by default only works when syncing and only for users that get added by that sync operation. So existing users will stay disabled and the bug in the UI is entirely separate from that (unfortunately). So the only workaround for existing users is to edit the user.cfg file...

You may also need to adapt the "authorized redirect URIs" on Google's side [1]. [1]: https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred

Sounds like your PDM host cannot reach the Google host here. Are you sure PDM is configured with sufficient access to the internet? We are aware of that and a fix has already been send to the mailing list [1]. [1]...

Could be that you are running into a previously patched issue [1], but version has been released that includes it yet [2]. So for now, you can either manually edit the file /etc/proxmox-datacenter-manager/access/user.cfg directly and add the line enable true to any account you want to enable...

This refers to the users state within PDM and not within your AD realm. Does the user appear as enabled when you look at the overview of users in the access control panel? I'll try to reproduce this one, sounds like a wiring issue. Sorry for the inconvenience.

Hallo, ja der Key muss "re-issued" werden, ist im Shop erklärt [1]. [1]: https://shop.proxmox.com/index.php?rp=/knowledgebase/6/Server-change---How-can-I-move-my-current-subscription-key-to-the-new-server.html

Fingerprints just identify the TLS certificate and probably aren't you problem here. The error message indicates that there is already a token by this name already exists on the remote. Either choose a different name for the token when adding the remote or log into the remote and remove the...

Yes there is already an open bug to track implementing groups for PDM [1]. The context there is LDAP/AD realms, but of course OpenID realms would be part of that too once we implement it. [1]: https://bugzilla.proxmox.com/show_bug.cgi?id=6883

I think you are misunderstanding something here. The remote configurations are not per user. You probably just haven't given your new user any permissions, so it does not see existing remotes. Simply configure appropriate permissions for the OpenID user in the Access Control menu.

Just so you are aware, BTRFS also suffers from write amplification [1]. If this is something you are very worried about, bitrot protections, such as checksums, will always incur extra overhead. Thus, you will always suffer from some degree of write amplification. However, BTRFS generally comes...

Yes, all remotes are only connected to via HTTPS. This depends on your setup. If everything is local in your network, a VPN may not be necessary. If you split your infrastructure across several networks, and it is not possible for PDM to connect to all remotes, then yes using a VPN or similar...

Maybe you misunderstood? This is not a general requirement. PDM uses the REST API of all remotes, so no SSH is involved. HTTP connections are secured via HTTPS/TLS. HTTPS certificates are verified by PDM either by fingerprint that will be saved when configuring a remote or via the trusted...

Hi this is a bug and has already been fixed and applied on latest git [1]. The next release should hopefully include this fix, thanks for reporting it anyway, though! [1]: https://git.proxmox.com/?p=ui/proxmox-yew-comp.git;a=commit;h=808a5c0c6a8a4c7ec5a285c9d585425e98d84f6b