starred/proxmoxer

Fork 0

mirror of https://github.com/proxmoxer/proxmoxer.git synced 2026-04-25 07:06:00 +03:00

[GH-ISSUE #178] proxmoxer.core.ResourceException: 500 Internal Server Error: #99

New issue

Closed

opened 2026-02-27 15:46:27 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 15:46:27 +03:00

Owner

Originally created by @laugrean on GitHub (Oct 11, 2024).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/178

From time to time I run into the resourceException listed below.
It does not matter which api endpoint i call.

proxmoxer.core.ResourceException: 500 Internal Server Error: b'{"digest":"0699a3f048f4fc792d091054901dcb7efb54579c8a93de3f2b81db4ab5cee7a2","errors":[],"files....
second call is without any errors
{'digest': '0699a3f048f4fc792d091054901dcb7efb54579c8a93de3f2b81db4ab5cee7a2', 'errors': [],

Any idea what's wrong here?

As background information:
python 3.11.5
openssh-wrapper==0.4
proxmoxer==2.0.1
proxmox ve 8.2.2

proxmoxer is using openssh to connect to my nodes.

Originally created by @laugrean on GitHub (Oct 11, 2024). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/178 From time to time I run into the resourceException listed below. It does not matter which api endpoint i call. proxmoxer.core.ResourceException: 500 Internal Server Error: b'{"digest":"0699a3f048f4fc792d091054901dcb7efb54579c8a93de3f2b81db4ab5cee7a2","errors":[],"files.... second call is without any errors {'digest': '0699a3f048f4fc792d091054901dcb7efb54579c8a93de3f2b81db4ab5cee7a2', 'errors': [], Any idea what's wrong here? As background information: python 3.11.5 openssh-wrapper==0.4 proxmoxer==2.0.1 proxmox ve 8.2.2 proxmoxer is using openssh to connect to my nodes.

kerem

2026-02-27 15:46:27 +03:00

closed this issue
added the
type:bug 🐞

backend:openssh
labels

kerem commented

2026-02-27 15:46:27 +03:00

Author

Owner

@jhollowe commented on GitHub (Oct 15, 2024):

If you feel comfortable doing a small change to the code and running from that modified version (pip install -Ue /path/to/clone/with/changes/), you can add a print(stdout, stderr) in command_base.py where it tries to parse the error that PVE returns.

If you can do this and then upload the (sanitized to remove any private names/IPs/etc) failing output, that would help a lot to understand what is causing the error when it occurs.

@jhollowe commented on GitHub (Oct 15, 2024): If you feel comfortable doing a small change to the code and running from that modified version (`pip install -Ue /path/to/clone/with/changes/`), you can add a `print(stdout, stderr)` in command_base.py [where it tries to parse the error](https://github.com/proxmoxer/proxmoxer/blob/f72466614a05b0c4f7505d5805a5eb232505cdea/proxmoxer/backends/command_base.py#L113) that PVE returns. If you can do this and then upload the (sanitized to remove any private names/IPs/etc) failing output, that would help a lot to understand what is causing the error when it occurs.

kerem commented

2026-02-27 15:46:27 +03:00

Author

Owner

@laugrean commented on GitHub (Oct 16, 2024):

Hey!
Thanks for the hint.
The ssh output like "Warning: Permanently added 'xxxx' (ECDSA) to the list of known hosts." or any other of those messages caused it.
I've now adapted the ssh config with LogLevel error, e.g.

Host *
StrictHostKeyChecking accept-new
LogLevel error`

But on our production system I've faced another problem.
If the ~/.ssh directory is not in place it is not created automatically. Maybe you can adapt this in future?

@laugrean commented on GitHub (Oct 16, 2024): Hey! Thanks for the hint. The ssh output like "Warning: Permanently added 'xxxx' (ECDSA) to the list of known hosts." or any other of those messages caused it. I've now adapted the ssh config with LogLevel error, e.g. >Host * > StrictHostKeyChecking accept-new > LogLevel error` But on our production system I've faced another problem. If the ~/.ssh directory is not in place it is not created automatically. Maybe you can adapt this in future?

kerem commented

2026-02-27 15:46:27 +03:00

Author

Owner

@jhollowe commented on GitHub (Oct 20, 2024):

that is interesting. As far as I know the openssh backend (or really the library the backend uses) does use the openssh installed on the system which I would have assumed would handle creating the ~/.ssh dir if it was e.g. writing to the known_hosts file.
Why is your fingerprint being written to the known_hosts file more than once on the initial connection?

I think managing the ~/.ssh dorectory is outside the scope of this project. If you have further issues with the openssh backend, you could try using the ssh_parimiko or https backends which should not rely on the ~/.ssh directory.

@jhollowe commented on GitHub (Oct 20, 2024): that is interesting. As far as I know the `openssh` backend (or really the library the backend uses) does use the openssh installed on the system which I would have assumed would handle creating the `~/.ssh` dir if it was e.g. writing to the known_hosts file. Why is your fingerprint being written to the known_hosts file more than once on the initial connection? I think managing the `~/.ssh` dorectory is outside the scope of this project. If you have further issues with the `openssh` backend, you could try using the `ssh_parimiko` or `https` backends which should not rely on the `~/.ssh` directory.

kerem referenced this issue

2026-02-27 15:46:46 +03:00

[PR #99] [MERGED] fix error handling for APIs that don't give a dict in the response #174

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxmoxer#99

No description provided.

Rows
Columns