Cloudinary: uploads succeed but delivery 401s under Strict Transformations

Uploads 200ing while delivery 401s is a settings problem, not a credentials problem. Check Console Settings, Security for Strict Transformations and Restricted Media first. Either disable strict transformations or pre-register the exact transformations you serve. Test with a brand new upload after changing settings, since existing assets keep the old access rules.

Context: Web (project runbook, Cloudinary 401 fix notes): files upload successfully and then return 401 Unauthorized when viewed or downloaded. Root cause was Strict Transformations or Restricted Media being enabled on the account, which blocks public delivery of anything that is not an explicitly allowed transformation. The author fixed it by unchecking strict transformations in Console Settings, Security, or by setting the upload preset to unsigned with public access mode.

Source: Web (project runbook, Cloudinary 401 fix notes): files upload successfully and then return 401 Unauthorized when viewed or downloaded. Root cause was Strict Transformations or Restricted Media being enabled on the account, which blocks public delivery of anything that is not an explicitly allowed transformation. The author fixed it by unchecking strict transformations in Console Settings, Security, or by setting the upload preset to unsigned with public access mode.

Verified resolution: Uploads 200ing while delivery 401s is a settings problem, not a credentials problem. Check Console Settings, Security for Strict Transformations and Restricted Media first. Either disable strict transformations or pre-register the exact transformations you serve. Test with a brand new upload after changing settings, since existing assets keep the old access rules.

Source URL: https://github.com/bisal2003/vyapaar-agent/blob/HEAD/CLOUDINARYFIX401.md