• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Content Security Policy

Status
Not open for further replies.

dhiananda

Chevereto Member
👉 Problem below

🎯 Description of the issue

With newer browser, like Firefox and Chrome, uploading images, will throw an error "Some files couldn't be added"

▶🚶‍ Reproduction steps
  1. Open browser, upload any images. using newest Chrome or Firefox.
  2. Click upload.
😢 Unexpected result

Error notice: "Some files couldn't be added"

📃 Error log message

Error log shown at the browser console:
Content Security Policy: The page’s settings blocked the loading of a resource at blob:https://domain.name/d0a6e403-2f6f-48ba-95f3-e6ba93a29136 (“default-src”).
I have set CSP for the img-src, too, but whatever I put there, the error still redirect to 'default-src'
This not happen with older browser, or even IE 11 have no problems.
Not sure why recent browser throw this error. Any tips without disabling CSP?
Thanks in advance.
 
Have you checked server error logs? I had this, and needed to increase php timeouts and max upload limits.

Nginx configs to apply if needed:
fastcgi_read_timeout 600s
client_max_body_size 20M;
 
Unfortunately, this ticket has more than seven days without a reply or feedback from the original poster. We will now consider this ticket abandoned and its now closed.

Don't hesitate to create a new ticket if this matter is still causing you issues.

Ticket closed.
 
Status
Not open for further replies.
Back
Top