https://datocms-assets.*.eu.r2.cloudflarestorage.com works and the client is now able to upload assets.I’m looking for confirmation that those whitelists are correct. Have you faced this before with other clients?
Thanks!
Thank you for letting us know!
I have not personally heard of this particular situation (where uploads are universally blocked)… while we do occasionally get questions about blocked uploads, the causes and solutions are almost never the same from one incident to the next. Sometimes it’s a Windows or Edge policy, sometimes it’s a regional network block, sometimes it’s a S3 bucket issue, sometimes a private DNS resolver issue, etc. We try to look at those on a case-by-case basis.
And we actually already have some upload troubleshooting logic in our upload UI… if they try to upload something and it fails, we’ll try to ping our R2 bucket from their machine and log its success/failure, then capture it in our error logging. The end result is that they should get an Dato error ID (that looks like a UUID), and if they send that to us, we can see their failed request and their OS & user agent and such, along with the originating IP address and network. It helps us troubleshoot their specific circumstances.
For now that should be correct, but we do change upstream providers from time to time. (It was formerly AWS, and changed to Cloudflare a year or two back).
Where in the docs or libraries do you think this would be most helpful? So far we’ve just been dealing with these issues case-by-case, but maybe not a bad idea to document it more explicitly somewhere (noting that they are subject to change in the future)?
Hi Roger,
Thanks for your confirmation! We’ll keep it AS IS for now and understand that if you switch upstream provider that we might have to adapt the whitelist.
Perhaps Media Area — DatoCMS is the right location for a small info banner?
Greetings
Thomas
I’ll try to provide a heads up if that happens. It’s very rare, though.
It’s probably not something we’d want to make user-visible in the UI (we don’t want to confuse editors who are not developers — for that we should already have a user-facing error popup, the UUID thing I mentioned earlier).
It could be mentioned in the API docs somewhere, though…