Viewing 1 replies (of 1 total)
  • Plugin Author DearHive



    This is CORS issue and this can be resolved by setting proper permissions in AWS S3. Some clients had different experiences with AWS settings and we suggested the following recently:

    Looks like AWS changed their configuration and now uses JSON Format by default.

            "AllowedHeaders": [],
            "AllowedMethods": [
            "AllowedOrigins": [
            "ExposeHeaders": []

    Explained at

    Best Regards,


Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.