Recent content by sterzy

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

Hm, by default firewall should be disabled. Can you run a small port scan of the Proxmox VE host to see what that results in? Should be doable with nmap -Pn <IP OF PVE HOST> from the host you are trying to connect from.

Are you sure there is no firewall in between you and the Proxmox VE host that blocks access to port 8006 from your VPN subnet? If you enabled the host firewall for your Proxmox VE host, you should also make sure that it accepts your connection on port 8006.

You currently can't use groups yet. This is a mistake in the documentation. However, there is already an open request for this feature [1]. Ah, yeah that should be cleaned up, sorry for that. [1]: https://bugzilla.proxmox.com/show_bug.cgi?id=6883

Alright, that means for the settings you are providing your AD realm expects some kind of authentication: Can you tell me the differences between your PVE and PDM AD realm exactly? Yes, currently a bind-dn is only supported in combination with a bind password. Are you using a bind-dn in...

Are you triggering that error by editing the realm through the UI? Please don't edit the realm through the UI. Instead, add the realm as intended to the file /etc/proxmox-datacenter-manager/access/domains.cfg. Then use the “Sync” Button in the UI under Configuration > Access Control > Realms. A...

Yes, due to naming conventions base_dn is used in our Rust code base, but the configuration expects base-dn. I understand this is confusing, though. In the configuration you should use base-dn. Yes, every time you try to update something, PDM will try to use the new configuration to query the...

The PDM (and PBS) implementations of our AD realm support try to guess the base-dn parameter from the default naming context that your AD realm uses. If this doesn't match the actual base-dn you want to use this won't work. For now, you should be able to add the realm manually by adding the...

Interesting that the error here is about missing authentication, are you sure that both address the same AD realm from the same network?

The license as with most of our products is AGPL so you can use PDM by yourself free of cost as you see fit. If you want to have proper enterprise subscription support and access to the Proxmox Datacenter Manager enterprise repository, at least 80% of all connected remotes need to have an...

The patch was applied in the meantime, so the fix will be implemented in the next version of pve-yew-mobile-gui ^^

Glad to hear it!

Can you make sure that the caches are empty, to reload the page, and that no realm is set as default realm and try again? This should work in that case. For the default realm bug, I have already sent a patch here [1]. So this will be fixed soon too. [1]...