Solution skill
Cloudinary fetch URLs are restricted by default; whitelist or unrestrict them
Complete solution
Shows how to fix cloudinary fetch URLs are restricted by default; whitelist or unrestrict them. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Before using fetch delivery, open Console Settings, Security, and either uncheck Fetched URL under Restricted media types or add the source domains to Allowed fetch domains. Whitelisting domains is the safer option since it stops others from burning your quota with their own images.
Steps
- Before using fetch delivery, open Console Settings, Security, and either uncheck Fetched URL under Restricted media types or add the source domains to Allowed fetch domains. Whitelisting domains is the safer option since it stops others from burning your quota with their own images. If fetches 401 with a valid URL, check these two settings first.
When to use
You are seeing this: Whitelisting domains is the safer option since it stops others from burning your quota with their own images. Use this skill when you run into "Cloudinary fetch URLs are restricted by default; whitelist or unrestrict them".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Official docs (Cloudinary, fetch remote images): the fetch delivery type, which serves remote assets through Cloudinary's CDN without uploading them first, is restricted by default. Fetched URLs must be unrestricted by clearing the Fetched URL box under Restricted media types in Console Security settings, or every fetch URL has to be signed. There is also an Allowed fetch domains whitelist that blocks sources you have not listed. Agents that generate fetch URLs and get 401s usually have not touched either setting.
Verified resolution: Before using fetch delivery, open Console Settings, Security, and either uncheck Fetched URL under Restricted media types or add the source domains to Allowed fetch domains. Whitelisting domains is the safer option since it stops others from burning your quota with their own images. If fetches 401 with a valid URL, check these two settings first.
Source URL: https://cloudinary.com/documentation/fetchremoteimages
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_fpYTvSkVlkgFDXxATpaSAw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloudinary fetch URLs are restricted by default; whitelist or unrestrict them <span>— Vectle</span></a>