Hi @devksec!
WP Offload Media Support Team here. Thanks for reaching out with your query! We would be happy to assist.
It seems you’re having trouble saving plugin settings, and that you’re using LiteSpeed Cache. We often see compatibility issues with LiteSpeed Cache and the LiteSpeed web server itself, which is why WP Offload Media currently supports only Apache and Nginx:
https://deliciousbrains.com/wp-offload-media/pricing/#requirements
We recommend trying to define your plugin settings using the AS3CF_SETTINGS constant in your wp-config.php file:
https://deliciousbrains.com/wp-offload-media/doc/settings-constants/
We hope this helps! Please let us know if you have more questions.
Thread Starter
dev
(@devksec)
Hello,
We have the AWS S3 bucket settings there already but i’ll review the others and set.
Theres a short window where we see the cloudfront domain move to the dedicated CNAME but it has this error (site redacted)
“Offloaded media URLs may be broken due to an invalid delivery domain. cdn.SITE.com did not resolve to an IP address”
However its the cname pointing at the cloudfront.net address, which does work when not using a customer cname.
Also, there doesn’t seem to be capabilities to customise the upload path pre-fix to include usernames or UUIDs for uploaded files, is this correct ?
Hi @devksec,
Thanks for the update. Regarding the delivery error, could you please confirm if you’ve followed our CloudFront guide here: https://deliciousbrains.com/wp-offload-media/doc/cloudfront-setup/
It includes steps for configuring a custom CNAME and ensuring everything resolves properly.
As for the upload path prefix, WP Offload Media allows some customization for the bucket path such as adding a prefix, enabling/disabling the year/month folders, and using object versioning. You may check the plugin settings doc here: https://deliciousbrains.com/wp-offload-media/doc/settings/
You might also find our Tweaks plugin helpful: https://github.com/deliciousbrains/wp-amazon-s3-and-cloudfront-tweaks
