PPDM: Upgrade Package Load Fails "Upload attempt failed. Click Upload Package and select the update for installation again"

Below error appears when attempting to upload upgrade package file to PowerProtect Data Manager from the portal:

Chrome har file shows the below error:

[x.har]

{
  "request": {
    "method": "POST",
    "url": "https://<ppdm_fqdn>/zuul/api/v2/upgrade-packages",
    "postData": { "params": [ { "name": "file", "value": "(binary)" } ] }
  },
  "response": {
    "_error": "net::ERR_CONNECTION_ABORTED",   <<<<< or net::ERR_TOO_MANY_RETRIES
  },
}

Missing nginx configuration parameters resulted in TLS Server Name Indication (SNI) hostname mismatch between the nginx reverse proxy and Zuul's embedded Tomcat which resulted in the HTML 400 status [HTML_BAD_REQUEST].

This issue is planned to be addressed in an upcoming PowerProtect Data Manager version.

In the interum, the below three workarounds are available to successfully upload the package.

• (1) Utilize the PowerProtect Data Manager IP address when connecting to the PowerProtect Data Manager UI and perform upgrade.
• (2) Manually upload the file to /data01/brs/upload and use this for upgrade.
• (3) Add two nginx directives to the /zuul/api/v2/upgrade-packages location block.

1. Connect to the PowerProtect Data Manager server using SSH as the admin user.

ssh admin@<PPDM_Server>

2. Backup the nginx configuration file before making changes.

sudo cp /etc/nginx/conf.d/default.conf /tmp/nginx-original-default.conf

3. Open the nginx configuration file to edit the nginx configuration file.

sudo vim /etc/nginx/conf.d/default.conf

4. Locate the Upgrade Packages API Configuration. Search for the following block: location /zuul/api/v2/upgrade-packages {
5. Update the /zuul/api/v2/upgrade-packages block by locating the following line: proxy_http_version 1.1;

Add the following parameters immediately after the line:

• • proxy_ssl_server_name on;
  • proxy_ssl_name $host;

The updated section should look similar to:

location /zuul/api/v2/upgrade-packages {
    ...
    proxy_http_version 1.1;
    proxy_ssl_server_name on;
    proxy_ssl_name $host;
    ...
        }

6. Save the file and verify the nginx configuration syntax.

sudo nginx -t

Expected result:

syntax is ok
test is successful

7. Restart nginx to apply the changes.

sudo systemctl restart nginx

8. Confirm that the nginx service is active and running.

sudo systemctl status nginx

Expected status:

Active: active (running)

9. Log in to the PowerProtect Data Manager UI and upload the upgrade package. Monitor the upload process and verify that it completes successfully without errors.
10. Cleanup.

sudo rm /tmp/nginx-original-default.conf