starred/project-pegaprox-PegaProx

Fork 0

mirror of https://github.com/PegaProx/project-pegaprox.git synced 2026-04-25 18:15:50 +03:00

[GH-ISSUE #67] Unauthorized when adding new cluster #46

New issue

Closed

opened 2026-03-02 15:47:29 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 15:47:29 +03:00

Owner

Originally created by @ry-ops on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/67

Originally assigned to: @mkellermann97 on GitHub.

Fresh install via deploy.sh, credentials verified working via curl, but UI returns "Unauthorized" when adding cluster with both password and API token auth.

Originally created by @ry-ops on GitHub (Feb 22, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/67 Originally assigned to: @mkellermann97 on GitHub. Fresh install via deploy.sh, credentials verified working via curl, but UI returns "Unauthorized" when adding cluster with both password and API token auth.

kerem closed this issue

2026-03-02 15:47:30 +03:00

kerem commented

2026-03-02 15:47:30 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Feb 22, 2026):

Hi @ry-ops ,

could you please check if you have the right permissions and if your port is 8006?
https://docs.pegaprox.com/#proxmox-permissions

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 22, 2026): Hi @ry-ops , could you please check if you have the right permissions and if your port is 8006? https://docs.pegaprox.com/#proxmox-permissions Regards, Marcus

kerem commented

2026-03-02 15:47:31 +03:00

Author

Owner

@ry-ops commented on GitHub (Feb 22, 2026):

Hi Marcus.

Thanks for the quick response!

Yes, confirmed on both fronts:
∙ Using the default root@pam user with LPAM
∙ Port is set to 8006

What’s puzzling is that credentials are verified working via direct curl against the Proxmox API — I’m getting valid responses back — but the UI still returns “Unauthorized” when adding the cluster regardless of whether I use password or API token auth.

Happy to pull logs or share any debug output if that helps narrow it down. Is there a specific log path or verbose mode in PegaProx

I should be looking at?

Thanks,
Ryan

@ry-ops commented on GitHub (Feb 22, 2026): Hi Marcus. Thanks for the quick response! Yes, confirmed on both fronts: ∙ Using the default root@pam user with LPAM ∙ Port is set to 8006 What’s puzzling is that credentials are verified working via direct curl against the Proxmox API — I’m getting valid responses back — but the UI still returns “Unauthorized” when adding the cluster regardless of whether I use password or API token auth. Happy to pull logs or share any debug output if that helps narrow it down. Is there a specific log path or verbose mode in PegaProx I should be looking at? Thanks, Ryan

kerem commented

2026-03-02 15:47:31 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Feb 22, 2026):

Hi @ry-ops ,
Thanks for the quick update!
It would be great if you could start PegaProx in debug mode to help us investigate. Unfortunately, this is a manual step:

SSH into your VM
Run systemctl stop pegaprox
Navigate to the installation folder: cd /opt/pegaprox
Run pegaprox_multi_cluster.py --debug

Then go to the UI and try adding your Proxmox Cluster again – the debug output should tell us why it's failing.
Also, feel free to send us a support bundle at support@pegaprox.com so we can also investigate here.

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 22, 2026): Hi @ry-ops , Thanks for the quick update! It would be great if you could start PegaProx in debug mode to help us investigate. Unfortunately, this is a manual step: SSH into your VM Run systemctl stop pegaprox Navigate to the installation folder: cd /opt/pegaprox Run pegaprox_multi_cluster.py --debug Then go to the UI and try adding your Proxmox Cluster again – the debug output should tell us why it's failing. Also, feel free to send us a support bundle at support@pegaprox.com so we can also investigate here. Regards, Marcus

kerem commented

2026-03-02 15:47:31 +03:00

Author

Owner

@ry-ops commented on GitHub (Feb 23, 2026):

Thanks for the insight Marcus. It ended up being a VLAN issue. It's up and working. I appreciate the support.

@ry-ops commented on GitHub (Feb 23, 2026): Thanks for the insight Marcus. It ended up being a VLAN issue. It's up and working. I appreciate the support.

kerem commented

2026-03-02 15:47:31 +03:00

Author

Owner

@mkellermann97 commented on GitHub (Feb 23, 2026):

Hi @ry-ops ,
Great to hear it's working now! VLAN issues can be tricky to track down.
And thanks again for all the PRs – really appreciate your contributions!

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 23, 2026): Hi @ry-ops , Great to hear it's working now! VLAN issues can be tricky to track down. And thanks again for all the PRs – really appreciate your contributions! Regards, Marcus

kerem referenced this issue

2026-03-02 15:47:53 +03:00

[PR #46] [MERGED] Improve ressources graphs #94