Hi,
Can you tell us which storage provider you are using and if you are using a CDN for delivery, which one you are using? Did you see any error messages in the debug log that could provide more details?
The settings notice for delivery generally works like this:
- Upload a file to the storage provider and set it to public access (default) and if that succeeds, try to access that file via the configured delivery provider.
- Upload a file to the storage provider and set it to private access and if that succeeds, try to access that file via the configured delivery provider.
Sounds like the tests detected a problem on step 1 above. Would be great if you also can copy the exact message and share it here.
-et
we added the reverse proxy to our site which is now being served by our CDN. I decided to make this change online without the update a month ago because unfortunately there is still an issue inside the delivery tab stating “
Private media is currently exposed through unsigned URLs. Restore privacy by verifying the configuration of private media settings.”
To my knowledge there isnt private media that is uploaded, correct? we arent using the assets (yet) so it should all be public. When I upload after the update it still goes to the s3 bucket. so Im assuming this is just a false alarm?
Hi @innovationv,
Thank you for the update. That message shows up for when a private file can be accessed using an unsigned URL. This happens during the plugin’s testing of the public and private delivery from the bucket using test files.
Can you kindly verify the configuration of private media settings as suggested from the error message? If you’re using CloudFront, you may refer to this guide:
https://deliciousbrains.com/wp-offload-media/doc/serve-private-media-signed-cloudfront-urls/
