Suggestions

liptech

Active Member
Jan 14, 2021
48
11
28
44
Brasil
Comments and Suggestions

I found the idea really interesting and I believe the team responsible for the suggestion should receive greater recognition for it.


Installation and operation

I installed the PDM in my environment and, early on, I found that some features are not operating as expected, while others are still in the implementation phase.


Visual

Proxmox 8.3 interface is very well structured, and visual identity plays a crucial role in the familiarity of users.
Although technology evolves rapidly, I see no reason to change something that is already widely accepted.

Also, I miss a chart that presents the use of the discs.
This data is as important as the others, but it is currently only available to VMs.
It would be ideal that both PDM and PVE include information on the use of discs, facilitating more complete analysis.


Users

I tried to create a user with exclusive permission for visualization, but could not assign any specific permission during the process.
When accessing the panel with this user, I realized that the cluster information registered in the PDM was not visible.

It would be very interesting for users to have access to pre-configured remote data, respecting their individual permissions.
Thus, Dashboard could also function as a monitoring tool.


ADD Remote

The “Remote Id” field could be renamed for “cluster name” as this designation better reflects its function.



A question:

I use the PBS the ACME Let's Encrypt for the SSL certificate.
Whenever the certificate is updated, I need to manually update the fingerprint (fingerprint) in the cluster.
Will this situation be repeated in PDM?
It would be very convenient if this process could be automated.
 
I use the PBS the ACME Let's Encrypt for the SSL certificate.
Whenever the certificate is updated, I need to manually update the fingerprint (fingerprint) in the cluster.

Remove the fingerprint in PVE. You do not need the fingerprint if you have Let's Encrypt TLS certificates and connect using a hostname covered by that TLS certificate.

There is a fingerprint because the starting TLS certificate is self-signed and, therefore, not trusted. The fingerprint is used to validate the TLS certificate presented. If you have a Let's Encrypt TLS certificate, it is validated using the root certificates in the operating system. If you use the Let's Encrypt certs and the fingerprint, you must update the fingerprint every sixty days.

Will this situation be repeated in PDM?
I would expect it will be. So, use Let's Encrypt and do not use the fingerprint.
 
Remove the fingerprint in PVE. You do not need the fingerprint if you have Let's Encrypt TLS certificates and connect using a hostname covered by that TLS certificate.

There is a fingerprint because the starting TLS certificate is self-signed and, therefore, not trusted. The fingerprint is used to validate the TLS certificate presented. If you have a Let's Encrypt TLS certificate, it is validated using the root certificates in the operating system. If you use the Let's Encrypt certs and the fingerprint, you must update the fingerprint every sixty days.


I would expect it will be. So, use Let's Encrypt and do not use the fingerprint.

It worked very well, thanks.


But I need another help from the "Subject Alternative Names", how can I add alternative names with the plugin?

I already tried with "," ";" and "Space" but the component does not allow.

Can you help me?


My interaction is that he has a pbs.lab .......
 

Attachments

  • Captura de tela de 2025-04-05 14-20-11.png
    Captura de tela de 2025-04-05 14-20-11.png
    49.9 KB · Views: 4
  • Like
Reactions: weehooey-bh
It worked very well, thanks.
You are welcome. :-)

But I need another help from the "Subject Alternative Names", how can I add alternative names with the plugin?

Use the Add button with the same plugin.
 

Attachments

  • Captura de tela de 2025-04-05 14-20-11 EDIT.png
    Captura de tela de 2025-04-05 14-20-11 EDIT.png
    58.3 KB · Views: 7