[Feature] "Reboot Node" (and potentially "Shutdown Node") added as an action item?

[ZoltrixGFC]

Describe the feature

Currently, I'm attempting to use PegaProx as an incredible single pane of glass for monitoring and managing individual Proxmox nodes (not clusters), but it lacks the ability to execute reboots on the nodes themselves (or I can't find it?). If an isolated host requires a reboot (e.g., after applying kernel updates), the user has to leave the PegaProx UI entirely, open a native Proxmox tab, or launch an external SSH terminal just to bounce the node.

Use Case

Would be great if possible to see "Reboot Node" (and potentially "Shutdown Node") added as an option.

Alternatives considered

Leaving the centralised PegaProx dashboard to log back into individual, standalone Proxmox VE web interfaces or handling reboots manually via an external CLI tool.

How important is this for you?

For users leveraging PegaProx to centralise isolated, standalone Proxmox hosts rather than traditional multi-node clusters, this addition bridges a major gap, keeping the admin completely inside a single management pane for day-to-day lifecycle maintenance.

Checklist

• I have searched existing issues and discussions to make sure this hasn't been requested before

[MrMasterbay]

Hi @ZoltrixGFC ,

you need to activate the maintenance mode and then you are able to reboot the system.
This is a safeguard feature actually that there can't happen any upsies.

Feel free to drop something in the jar to keep the project alive: opencollective.com/pegaprox

-NS

[MrMasterbay]

I will close this issue feature request also by now because its made by design like that :) .

[ZoltrixGFC]

@MrMasterbay thanks for the tip, but I can't place any node into maintenance mode:

Assuming this is because they are standalone nodes, not a cluster?

[MrMasterbay]

Oh @ZoltrixGFC does it stay like that?

Normally you should be able to skip the migration after a while.
Regards

[ZoltrixGFC]

@MrMasterbay yep left it for maybe 5 minutes, but it stayed like that. Eventually I rebooted the server that I am running PegaProx on, and the error cleared.