Recent content by jhollowe

Is anyone able to confirm if a single request for the ticket is viable for users with TOTP enabled?

Previously (in 7.x at least), you were able to include otp in a single request to /api2/json/access/ticket which would verify both the username/password and TOTP token and immediately provide a ticket and CSRF token. However, this appears to no longer work and requires the two-request flow the...

I imagine this is related to changes in http-server related to handling `Content-Type` on the file's multipart. RFC 2388 specifies that the `Content-Type` on multi-parts is optional. Chrome (and chromium-based browsers) have semi-recently started adding this header to its file uploads, but other...

I've created bug 4344 and submitted a patch to the mailing list.

I've done a packet capture against 7.1-7 (the latest ISO I had on hand) and 7.2-11 (same PVE node updated to latest). From what I can tell there is nothing wrong on the client side (the upload is the exact same request with different auth and multipart boundary). The request goes through fine...

It seems like this is related to this forum thread: https://forum.proxmox.com/threads/pveproxy-no-space-left-on-device-problem-with-storage-api.113451/ After some testing, it appears this error appears somewhere between 7.2-7 (works correctly) and 7.2-11 (broken while using same code as -7)

If you are looking for a way to do it in Python, you might want to check out the Proxmoxer library. It takes care of all the authentication and API call logic and just lets you call the endpoints you need. You can check out the readme in the repo or the new (still a work in progress)...

I'm quite familiar with the API Viewer website and at least the basics of many of the endpoints. However, in the course of using the WebUI there are some (or at least one) endpoints that do not appear in the API Viewer. For example, the /nodes/{node}/query-url-metadata endpoint is used by the...

When using the HTTPS API, it appears that the authentication method affects ISO uploads. When using standard username/password authentication, the upload works as expected. When using an API Token (for the same user with all the user's permissions), the upload fails and the Response is a 501...

I would like to be able to run some tests against the API for PVE (and PMG and PBS) but I don't want to have an entire instance of PVE installed. I know PVE needs its own kernel to work correctly (which cannot be guaranteed in a container) but I am not sure how much functionality is dependent on...

Is there a command line utility to interact with the PBS API similar to pvesh or pmgsh? I tried pbssh but that does not exist (or at least is not on the path).

If you look at the man page for fstrim, you can see this is due to how the verbose flag works:

It would be nice to allow it to use "=" as a separator for the token value. While the client does have to rebuild the string, it would make interacting with the APIs nicer if they all follow the same rules for formatting. I got other paths working correctly. I was using /access/users and it was...

I'm one of the maintainers of the proxmoxer python library and I'm trying to get it working with PBS. I have several issues when trying to get the API tokens working. They work perfectly with PVE, but there seem to be issues/differences with PBS. Why is the separator for the token id from the...

I found that using the html mode for the login (/access/ticket) properly set the cookie which works for the rest of my requests