[BETA] [HPE] HPE-VME - Failed to upload the worker image: Cluster is unavailable

[RSB]

Hi,

We've just installed the HPE VME plugin for Veeam on a newly deployed 3-node HPE VME cluster (non-slipstreamed/fresh Ubutntu with the VME installed on top) and are hitting an error when testing the worker deployment:

Failed to upload the worker image: Cluster is unavailable

We have veeam debug logs enabled, but the short version is the error message:

Code: Select all

2026-01-08 15:31:27.5269 00029 [12556] ERROR | [Morpheus][xxx Test][41ee12dc-4adb-4f75-9cf1-458aa3a1cec8]:  <== Request "Post" "https://xxx/api/virtual-images/1134/upload?filename=HpeMorpheusVmeWorker_13.1.0.206.qcow2", headers: "[Authorization: ***]", cookies: "[XSRF-TOKEN: ***]", body: "{}"
2026-01-08 15:31:27.5269 00029 [12556] ERROR | [Morpheus][xxx Test][41ee12dc-4adb-4f75-9cf1-458aa3a1cec8]:  ==> Response "Post" "https://xxx/api/virtual-images/1134/upload?filename=HpeMorpheusVmeWorker_13.1.0.206.qcow2", "code: 413", duration: "10 sec 91 msec", headers: "[CF-RAY: xxx", cookies: "[]", body: ""
2026-01-08 15:31:27.5269 00029 [12556] ERROR | [Morpheus][xxx Test][41ee12dc-4adb-4f75-9cf1-458aa3a1cec8][HpeImageUpdater]: Failed to upload the virtual image "HpeMorpheusVmeWorker_13.1.0.206.qcow2": An exception occurred while processing the API request. HttpErrorCode: RequestEntityTooLarge, HttpRequestError: . Message: Veeam.Vbf.Rest.Common.ClientGeneration.ApiException: Cluster is unavailable
2026-01-08 15:31:27.5269 00029 [12556] ERROR | [Morpheus][xxx Test][41ee12dc-4adb-4f75-9cf1-458aa3a1cec8][HpeImageUpdater]:  ---> System.Net.Http.HttpRequestException: Request failed with status code RequestEntityTooLarge

We've removed and re-added the plugin as well as update the server / re-add the HPE VME cluster into veeam.

Please advise on next steps.

Kind Regards,

Rashpal

[EvgenyBaev]

Hello,

Could you please review the Nginx configuration files on your HPE VME manager machine?
In my environment, these files are located in /opt/morpheus/embedded/nginx/conf/sites-enabled.

Typically, there should be no restrictions on client_max_body_size in the section for /api/virtual-images. For reference, here is an example configuration from our lab:

Code: Select all

location /api/virtual-images {
    client_max_body_size 0;
    proxy_buffering off;
    proxy_request_buffering off;
    proxy_set_header X-Real-IP  $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $host;
    proxy_http_version 1.1;
    proxy_pass http://localhost:8080;
}

In my testing, I was only able to reproduce the issue when I manually set a restrictive value for client_max_body_size (for example, client_max_body_size 50M;) and then reloaded Nginx using:

Code: Select all

/opt/morpheus/embedded/nginx/sbin/nginx -s reload

For your reference, the size of our image is 970.2 MiB.

Please let me know if you have any questions or need further assistance.

[RSB]

Hi,

We use an all-in-one Morpheus 8.0.12 machine to manage our HPE VME nodes - this is the only machine that seems to have the nginx configs on it. I've checked the config you posted - ours seems identical. It looks very "default" for the most part for both the Morpheus and Morpheus-ssl files within that directory though there are protocol specific code blocks - e.g. the morpheus-ssl config includes this at its start:

server {
listen 443 ssl;
http2 on;
server_name xxx;
access_log /var/log/morpheus/nginx/morpheus-ssl-access.log;
ssl_certificate /etc/morpheus/ssl/xxx.crt;
ssl_certificate_key /etc/morpheus/ssl/xxx.key;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
ssl_protocols TLSv1.2;
ssl_prefer_server_ciphers off;
ssl_session_timeout 5m;
ssl_session_cache builtin:1000 shared:SSL:10m;
ssl_session_tickets off;
ssl_dhparam /etc/morpheus/ssl/dhparams/dhparams.pem;
root /var/opt/morpheus/nginx/storage;
proxy_read_timeout 300;

I did try the nginx reload and a retry of testing the worker, but i still get the same error.

Regards,

Rashpal