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 #86] SSH Shell not access #62

New issue

Closed

opened 2026-03-02 15:47:38 +03:00 by kerem · 9 comments

kerem commented

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

Owner

Originally created by @ccesario on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/86

Originally assigned to: @mkellermann97 on GitHub.

Hi team,

Currently when I try PVE Host Shell, I got this error.

Is there any special config to enble it? Or is it a possuble bug ?

Best regards

Carlos

Originally created by @ccesario on GitHub (Feb 26, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/86 Originally assigned to: @mkellermann97 on GitHub. Hi team, Currently when I try PVE Host Shell, I got this error. <img width="555" height="483" alt="Image" src="https://github.com/user-attachments/assets/c3def11d-ce04-46a0-9c7b-a43d890c0969" /> Is there any special config to enble it? Or is it a possuble bug ? Best regards Carlos

kerem closed this issue

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

kerem commented

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

Author

Owner

@MrMasterbay commented on GitHub (Feb 26, 2026):

Hi @ccesario ,

thanks for the report I see it was probably from a latest pull request that killed here the shell.
We will push out an update later this evening this should fix it again.

Regards,
Nico

@MrMasterbay commented on GitHub (Feb 26, 2026): Hi @ccesario , thanks for the report I see it was probably from a latest pull request that killed here the shell. We will push out an update later this evening this should fix it again. Regards, Nico

kerem commented

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

Author

Owner

@ccesario commented on GitHub (Feb 26, 2026):

Hi @MrMasterbay,

Thank you by your feedback. I will wait the fix.

best regards,

Carlos

@ccesario commented on GitHub (Feb 26, 2026): Hi @MrMasterbay, Thank you by your feedback. I will wait the fix. best regards, Carlos

kerem commented

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

Author

Owner

@CoolWolf69 commented on GitHub (Feb 27, 2026):

Hello @MrMasterbay ,

just as a side note:
If you are trying to use a SSH Key, the message will be like this:

SSH key error: module 'paramiko' has no attribute 'DSSKey'

Hope your update will include the fix for this as well.

THANKS a lot for your good work!
Regards,
Wolle

@CoolWolf69 commented on GitHub (Feb 27, 2026): Hello @MrMasterbay , just as a side note: If you are trying to use a SSH Key, the message will be like this: `SSH key error: module 'paramiko' has no attribute 'DSSKey'` Hope your update will include the fix for this as well. THANKS a lot for your good work! Regards, Wolle

kerem commented

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

Author

Owner

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

Hi @CoolWolf69 Wolle,

Thanks for letting us know! This will be fixed in today's version.
Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 27, 2026): Hi @CoolWolf69 Wolle, Thanks for letting us know! This will be fixed in today's version. Regards, Marcus

kerem commented

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

Author

Owner

@CoolWolf69 commented on GitHub (Feb 27, 2026):

Thanks @mkellermann97 .... just got informed about the new available version now and indeed both - PW and SSH Key - are workign as expected! That was fast ... ;-)

Regards,
Wolle

@CoolWolf69 commented on GitHub (Feb 27, 2026): Thanks @mkellermann97 .... just got informed about the new available version now and indeed both - PW and SSH Key - are workign as expected! That was fast ... ;-) Regards, Wolle

kerem commented

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

Author

Owner

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

Hi @CoolWolf69,
You're welcome! Our current target SLA for customers is around 1 business day :).
That said, this update has been cooking for about 3 weeks now – it's a big one!

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 27, 2026): Hi @CoolWolf69, You're welcome! Our current target SLA for customers is around 1 business day :). That said, this update has been cooking for about 3 weeks now – it's a big one! Regards, Marcus

kerem commented

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

Author

Owner

@CoolWolf69 commented on GitHub (Feb 27, 2026):

Hello @mkellermann97 ... the addition of PBS is definitely what I was looking/hoping for. Will be tested at the weekend for sure - YEAH!

Regards,
Wolle

@CoolWolf69 commented on GitHub (Feb 27, 2026): Hello @mkellermann97 ... the addition of PBS is definitely what I was looking/hoping for. Will be tested at the weekend for sure - YEAH! Regards, Wolle

kerem commented

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

Author

Owner

@ccesario commented on GitHub (Feb 27, 2026):

Hi @mkellermann97,

Even after upgrade to 0.9.0 Im getting the same problem.

PegaProx
Beta 0.9.0

Multi-Cluster Proxmox Management

Build 2026.01 • © 2025-2026 PegaProx Team

@ccesario commented on GitHub (Feb 27, 2026): Hi @mkellermann97, Even after upgrade to 0.9.0 Im getting the same problem. ``` PegaProx Beta 0.9.0 Multi-Cluster Proxmox Management Build 2026.01 • © 2025-2026 PegaProx Team ```

kerem commented

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

Author

Owner

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

Hi @ccesario,

thanks for letting us know! The "Build 2026.01" you're seeing tells me your frontend didn't fully update - the current build should show 2026.02.

Can you try these steps:

Hard refresh your browser: Ctrl + Shift + R (or Cmd + Shift + R on Mac)
If that doesn't help, clear your browser cache for the PegaProx URL
Verify the file on your server is actually updated:
```
head -5 /opt/pegaprox/web/index.html
```
It should show Version: 0.9.0.1 Beta in the comment header.

If it still shows the old version, try running the update again:

cd /opt/pegaprox && ./update.sh --force

Let me know if that resolves it!

Regards,
Marcus

@mkellermann97 commented on GitHub (Feb 27, 2026): Hi @ccesario, thanks for letting us know! The "Build 2026.01" you're seeing tells me your frontend didn't fully update - the current build should show **2026.02**. Can you try these steps: 1. **Hard refresh** your browser: `Ctrl + Shift + R` (or `Cmd + Shift + R` on Mac) 2. If that doesn't help, clear your browser cache for the PegaProx URL 3. Verify the file on your server is actually updated: ```bash head -5 /opt/pegaprox/web/index.html ``` It should show `Version: 0.9.0.1 Beta` in the comment header. If it still shows the old version, try running the update again: ```bash cd /opt/pegaprox && ./update.sh --force ``` Let me know if that resolves it! Regards, Marcus

kerem referenced this issue

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

[PR #62] [MERGED] fix(ssh): guard ssh_user extraction against None api_user #100