JCDS Package Downloads Failing with HTTP 403 for All Packages in Jamf Cloud Tenant

Hello Jamf Support Team,

We are experiencing an issue in our Jamf Cloud environment where all package deployments are failing during the package download stage.
 

Environment

• Jamf Cloud URL: https://flexera.jamfcloud.com
• Managed macOS devices
• Policies are successfully received by clients
• Package downloads from JCDS fail with HTTP 403

Issue Summary

The Jamf client successfully communicates with the Jamf Pro server, retrieves policies, and begins package caching. However, when the client attempts to download the package from JCDS, the download fails with HTTP 403.

This issue is occurring for:

• CSIA package deployment
• Cyberduck package deployment
• Evernote package deployment
• Newly uploaded test package

Because multiple unrelated packages fail in the same way, this does not appear to be package-specific.

Sample Client Log

Plain Text

Executing Policy CSIA

Caching package csiaagent...

Downloading https://flexera.jamfcloud.com/jcds/v2/downloads/csiaagent.dmg

Error: Package was not successfully downloaded. 403

The network connection was interrupted while downloading the package.

Error: csiaagent.dmg is not available on the HTTP server.

`

Another example:

Plain Text

Executing Policy AppPortal_Evernote for Mac cloud 002_17_Install

Downloading https://flexera.jamfcloud.com/jcds/v2/downloads/Evernote-10.105.4-mac-ddl-stage-20240910164757-a2e60a8d876a07eded5d212fa56ba45214114ad0.dmg

Error: Package was not successfully downloaded. 403

Error: Evernote-10.105.4-mac-ddl-stage-20240910164757-a2e60a8d876a07eded5d212fa56ba45214114ad0.dmg is not available on the HTTP server.

Troubleshooting Performed

1. Verified client enrollment and connectivity.
2. Verified policies are successfully retrieved by the Jamf client.
3. Tested multiple existing packages.
4. Uploaded and tested a new package.
5. Confirmed identical behavior across different packages.
6. Followed the Jamf Community article regarding HTTP 403 errors and discovered an expired certificate.
7. Renewed and pushed the certificate.
8. Retested deployments after certificate renewal.
9. Issue persists with the same HTTP 403 error.

Request

Could you please investigate the following for our tenant:

1. JCDS health and availability.
2. Cloud Distribution Point configuration.
3. Package storage integrity in JCDS.
4. Package synchronization status.
5. Download token generation and authorization.
6. Any tenant-level permissions or backend storage issues.
7. Whether there are any known issues affecting package downloads for our Jamf Cloud instance.

Impact

All package deployments are currently blocked because clients cannot download packages from JCDS.

Thank you for your assistance.