mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 10:05:56 +03:00
[GH-ISSUE #80] Update & Reboot using non accessible IP #60
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ion-Storm33 on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/80
Originally assigned to: @MrMasterbay on GitHub.
Update & Reboot is using non accessible storage network IP address.
Steps to reproduce:
Proxmox host with multiple IP addresses. Some of the IP addresses are accessible to PegaProx and some are not accessible.
Put node in maintenance mode then started Update & Reboot
I receive the following message right away:
After a little while I receive this error:
How can PegaProx use the correct DNS name or IP address for host management tasks?
Thanks,
@MrMasterbay commented on GitHub (Feb 24, 2026):
Hi @Ion-Storm33,
this is sadly a known issue we will include a patch on sunday that should fix that :).
Best Regards,
Nico
@MrMasterbay commented on GitHub (Feb 27, 2026):
Hi @Ion-Storm33 ,
please see our newest patch and check if its now fixed :).
Best regards,
Nico