2 min read 2 wks ago

Could not create private storage

Your existing results and your trash are safe. The scan stopped before doing anything if you see this message.

Media Cleaner keeps its trash and logs in a private folder inside wp-content, so they can’t be reached from the web. Your server isn’t letting WordPress create that folder, usually because wp-content isn’t writable by the web server user. This can start happening after a host migration, a security plugin change, or a hosting permissions update.

You can fix it in either of two ways:

  • Let WordPress write to wp-content. Through your host’s file manager or over SFTP, give the web server user write permission on wp-content. Typically that means permission 755, owned by the web server user. Your host can do this for you if you’re unsure. Then run the scan again.

  • Choose another location. If you’d rather keep wp-content locked, add this line to wp-config.php above the line /* That's all, stop editing! */:define( 'WPMC_TRASH_DIR', '/home/youraccount/media-cleaner/trash' ); The folder that contains trash (here, /home/youraccount/media-cleaner) must exist and be writable by PHP. It must also be outside your uploads folder. Media Cleaner creates its private folder there.

If the scan still won’t start after that, open the dashboard’s environment check. It shows whether private storage is ready. Please send us a screenshot of it.