Search results

I have reverted the patch to try to work around the original problem. And I found out things are worse than we thought. After removing the extra headers from the 'content' part the request is accepted and a file is uploaded. But the uploaded file is corrupted – it has part of the headers of the...

The problem is that this line from the patch: $hdl->{rbuf} =~ s/^(.*?)(${delim_re})/$2/s; Won't match anything if the part delimiter does not come in the same data chunk as the one currently processed. The next line becomes nonsense, as '$1' is not what it is supposed to be, $hdl->{rbuf} is...

I have applied the patch and now the upload fails with: pveproxy[1730382]: problem with client ::ffff:10.28.45.85; No space left on device Which is strange, as there is plenty of disk space available there.

Here they are: Failing request: POST /api2/json/nodes/NODE/storage/STORAGE/upload HTTP/1.1 Host: HOST:8006 User-Agent: curl/7.75.0 Accept: */* CSRFPreventionToken: [REDACTED] Cookie: PVEAuthCookie=[REDACTED] Content-Type: multipart/form-data; boundary=yERt1dYNCtjX46clu06uO3ym2Y0cLUwb3nz...

Manual upload does work. Requests made with curl also work But our client code uses Apache HttpClient Java library to build the requests which are somehow different form those of curl. It seems like pveproxy is confused by the 'Content-Type:' and 'Content-Transfer-Encoding:' headers added by...

Thank you, the reasons are clear now. Though, this solution makes usability of this feature quite limited. Not everybody who needs to upload an image also needs network configuration permissions. Other software solves similar problem by blocking access to 'internal' networks (private IP ranges)...

I have mentioned problems with image upload via API in another thread. As a workaround I tried to use the 'download from URL' feature, but it seems unavailable for our operators. The API documentation for 'download-url' says it requires 'Sys.Audit' and 'Sys.Modify' permissions for / in addition...

Hi, We have upgraded our cluster from 7.1 to 7.3 and everything is fine… except ISO image uploads via API do not work any more for us. We get an error: {"data":null,"errors":{"content":"invalid format - invalid content type 'Content-Type: text/plain; charse...

That works. Thanks!

Hi, We are building application to manage VMs on a PVE cluster. This application is supposed to be limited to a specific VM pool, so it is granted PVEVMAdmin role on that pool. When I am trying to list VMs currently in the pool I get permission error: $ curl -ki -b "PVEAuthCookie=..."...