Skip to main content

Cloudinary crash Strapi admin



  • Aleksandar Kostadinov

    Hi @Studio Creatic,

    Looking a the code you shared, the env() expects an environment variable name but you are passing the raw values which it won't be able to use.

    Could you please make the following changes below -


     providerOptions: {
          cloud_name: env('doe4mucdz'),
          api_key: env('992987985328476'),
        api_secret: env('********************'),


     providerOptions: {
          cloud_name: env('CLOUDINARY_NAME'),
          api_key: env('CLOUDINARY_KEY'),
        api_secret: env('CLOUDINARY_SECRET'),

    And then restart the server and let me know if that works for you?

    If not, are there any logs on your backend that show any server-side error/exception that may provide more insight into the blank page you are seeing? In addition, are there any client-side errors in the browser console, any failed requests in the Network tab?

  • Studio Creatic

    hello, thank you for your quick return, if everyone was as responsive as you I would have finished my project 1 month ago! I modified the plugins file but still the blank page. I have a message in the console :

    Content Security Policy: Parsing of 'script-src-attr' failed because the directive is unknown.
    Content Security Policy: Page settings prevented an inline ("script-src") resource from loading. moz-extension:2113:49
    Content Security Policy: Page settings prevented a resource from being loaded at eval ("script-src"). 2 blob:27:22
  • Studio Creatic

    when i enter on content-manager, the backend crash and i have a another message :

    Not Found
    Transfert944 o (taille 94 o)

    Before installing Cloudinary i already had data in my Strapi backend, including images. can it come from this?
  • Eric Pasos


    I have provided some information on the internal ticket you've created and, additionally, I checked the file thumbnail_pexels_photo_2959192_3f3786515f.jpeg in our system logs and this does not exist.

    Hope to see your response on the ticket so we could continue verifying the processing issue for your application.



Post is closed for comments.